Illegal Filesystem characters in revision names

[David Allouche]

On Wed, 2005-12-07 at 09:00 -0500, Kevin Smith wrote:
> David Allouche wrote:
> > For what it's worth, probably not much, I agree with Robert and Aaron.
> > 
> > The inability to represent some names in some file-systems translates
> > into an internal limitation of the store using that file-system as a
> > back-end. It should be the store's responsibility to do any translation
> > required by the back-end it chooses to use. 
> 
> I'm not sure whether the following is a legitimate concern or not, 
> because I don't understand bzr internals enough, and haven't been 
> following this thread quite closely enough. Seems worth mentioning, though.

I think that is a legitimate concern.

> The potential problem I see with this is when the same on-disk store is 
> used by multiple clients with different operating systems. Samba shares 
> of FAT32 drives, burnt CD-ROM archives, and plain-http repositories come 
> to mind as ways this could happen.
> 
> It would be somewhat tragic if you couldn't burn a backup of a bzr repo 
> from a Win32 box, restore it to your Linux box, and have it work.

I think it would be reasonable for file-system based stores to do name
translations necessary to cope with the naming limitations of all known
systems.

-- 
                                                            -- ddaa
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051207/ace8ebfe/attachment.pgp