Interop between case insensitive file systems and case sensitive file systems

Jelmer Vernooij jelmer at
Mon Mar 19 22:48:57 GMT 2007

On Tue, 20 Mar 2007 09:26:49 +1100
"Andrew King" <eurokang at> wrote:
> I instead think it must be necessary in the long term to be able to
> create a repository with an option or something
> --normalised-file-names, that will not allow and to be
> added in the same location. Otherwise, the problem I had this morning
> (which I could only solve by reverting) will never be able to be
> prevented.
I think at the very least it could be useful to warn the user when
files are being added that can't exist portably. Case sensitive
filenames are an example of this, but other problematic items are
filename length limits, or invalid characters (ASCII/Unicode characters
1 through 31, ", <, >, |, \b, \0, \t).


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 307 bytes
Desc: not available
Url : 

More information about the bazaar mailing list