> The trouble with pre-commit hooks imho is that you are doing damage control
> rather than prevent damage from happening.
> For a long term solution I think that is not the right direction.
Agreed, but since backward compatibility has to be maintained, there
is always a way to commit file.C and then commit it as FILE.C from a
NCS system. Something should guard NCS systems from doing that.
> The same is also true for the -ncs flag to some extent, do you really want to
> forever have to specify the -ncs option?
Me? Nooo.. the TSVN for example :))
It may not be a flag, may be a "setting per client" - per IP, per
>>>It also involves an understanding of your platform and your file system
>>>for the client _and_ server machine you are working with.
Server does not matter, for the client...
Well Windows users are happy when the things involve gui, not
commandline. If some of the most-popular windows GUIs (TSVN) are
updated, then all users will receive the benefit
>>>I would be more open to a new property called "svn:case-insensitive"
>>>which acted like the "svn:executable" property. If set the client
>>>performs a well defined, deterministic action on the file/directory.
>>>This action could be munging all the file names to lower case, upper
>>>case or something else.
>> There is one problem with this approach - the properties gets stored
>> and distributed so there is a nice chance someone with CS system to
>> checkout folder that has this property set from an NCS system.
> and of course not all clients use the same action, and we have chaos...
We have a chaos now too :)
> In other words, the 'action' needs to be consistent over all machine in the
> project, which in turn makes it possible to do this action at the moment of
> adding the file only, which in turn means the svn:case-insensitive flag is not
Utopia... there is no way to handle all cases, a global server
setting will do work but that's not a solution too. There will be
always a way some client to "cheat" but if someone really wants to
screw it up, he can do it :)
> (maybe it is just me, but I cannot really imagine how a *file* can be case
I can't imagine the opposite... how can file.c and file.C be different
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Aug 23 13:57:20 2005