> Remember, it's the *filesystem* that cares about case, not the OS.
> I mount NTFS partitions on my Linux box all the time, and I'm still
> limited by NTFS, not Windows, you know?
Yeah but what's the point? The OS is referred by its native
filesystem, it's the same u say case sensitive os or case sensitive
file system. It is the same for the current discussion, means "Case
Sensitive source" and non-case sensitive one if you want it that way
:)
> IMHO, any source control tool shouldn't assume anything. If svn
> assumes what was asserted below, that's fine for windows. Should it
> assume other things for *nix users? I don't think a cross platform
> source control tool should bother making those kinds of OS-centric decisions.
Agreed, that's why I proposed a switch to "tell" it what to do so it
does not assume anything.
> I also think that a source control tool should not alter your
> source, even the file names (refer to the heated debate about code
> style and automation about a month ago.)
Not automatic, agree on code styles and so on, but when it's
explicitly said, then it's ok.
> All this being said, it seems to me this whole debate is about
> imposing common sense on the tool. This really hasn't come up *that*
> much in my 10 years of experience, and when it does, I just tell the engineer 'don't do that'.
No
> As somewhat of an aside, ClearCase had server options for 'Case
> Sensitive' and 'Case Preserving' which were actually kinda neat
> (even though it goes against my philosophy to have them at all.) I
> turned both of them off at the time, which essentially checked every filename in as all lowercase.
Server-side options is ok for working with either CS "filesystem" or
NCS one, not both.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 23 09:13:54 2005