[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: [TSVN] Wish: Case-insensitivity within files

From: McKenna, Simon (RGH) <Simon.McKenna_at_rgh.sa.gov.au>
Date: 2005-07-05 04:23:20 CEST

-> A better solution might be to write a pre-processor which
-> converts files into VB preferred format, so that VB never
-> wants to change anything.


How about a pre-commit hook, run "svnlook changed" on the
transaction, parse output, for each 'A'dded file, validate
for VB format (use regex?), then reject commit if necessary
with appropriate error message:

  "Added file xxx is not in standard VB file format,
   please rename to Xxx and commit again"

So it is independent of the client.

If you wanted to be flexible, you might like to setup a
Subversion property acting as a VB format flag on the
directory (or parent directories) containing the VB files,
like the flag used to trigger 'bugtraq' parsing.

That way, only files in those directories (or sub-dirs of
parents) which have the flag set get validated, so other
parts of your repository don't have to be so strict.

Robert, if you're willing to help out, I will add a target
to Subnant to accomplish this, there is code in existing
targets which already does some of the leg work, and the
framework is built. So it shouldn't be too hard.

It would be done using a simple spec, something along the lines of:
(the commit-email hook target has some of the code we could re-use)

You can find details on Subnant here:


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Jul 5 04:22:21 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.