> Not to be rude, but SVN allows you to reject mixed case commits with a
> hook script, but it will _never_ modify the transactions you create for
> commits.
Yeah, it only rejects them, while the truth for the NCS system is that
it has to accept both without damaging anything. I have said how, he has
said it too.
> The tool should not modify a commit, ever. No matter how trivial it may
> be. This is a more reliable implementation, but by no means robust -
> which is the motivation for hacks and fixes generated by poor
> development tools.
Poor development tools? If a development tool in a CS system generates
different case files then it is poor, but when the system is not it's
not a dev tool fault, it's not anybody's fault. Now, svn is written
with *nix in mind and not handling windows or macos well. So consider
changing sides - if someone has written svn with windows in mind and
it has no support for case at all - then should someone say "don't
touch it, it's fine, they have to realize that file.c and File.c are
the same? This is stupid, there are *no* crappy dev tools, crappy
filesystems or so on, there is just incomplete implementation handling
only half of the world. We are asking about the other half.
> I prefer reliable over robust in this case because subversion is very
> important as a revision control program. It should not interpret what a
> user _might_ have meant in a commit transaction.
I have written of a way this to be done, if you can tell me how it is
unreliable I'll back off.
> This topic is often discussed, please read the mail {user,dev} archives
> for more case insensitive discussions.
Yeah, have read them. There are quite lot of discussions, there are
quite lot requests on the TSVN mailing lists and forums too.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 22 20:55:04 2005