RFC: loosening file name limits

[Robert Collins]

So we have a number of limits on file names.

must be unicode
must not contain \\ and various other unportable characters
must serialise cleanly within our various storage formats

I think the first constraint is very useful for portability; the
following is not about that.

The second constraint can be regarded as bzr being a guardian - which
just gets in the way sometimes.

We don't guard against many other user-code portability issues like
having "README" and "Readme" in a single dir; I think we should get rid
of the second constraint in favour of a nag/warn system where unportable
tree layouts are [optionally] warned about but not prohibited.

Thoughts?

-Rob

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- 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/20080731/cfd32b73/attachment-0001.pgp