bad characters in filenames on windows

[Robert Collins]

On Tue, 2006-04-11 at 12:24 +1000, Martin Pool wrote:
> On 10/04/2006, at 5:01 PM, Robert Collins wrote:
> 
> > On Mon, 2006-04-10 at 10:07 +1000, Martin Pool wrote:
> >> On 09/04/2006, at 5:46 PM, Robey Pointer wrote:
> >>
> >>> It's been brought to my attention that the paramiko bzr tree is
> >>> unusable on Windows because of illegal characters in filenames or
> >>> revision names.  Supposedly this can be fixed by some manual
> >>> process but will be fixed "better" in an upcoming bzr release where
> >>> metafiles are quoted.
> >>>
> >>> Is 0.8 that release? :)
> >>>
> >>> Is there something I can do using an up-to-date bzr.dev that will
> >>> fix the paramiko branch for Windows users?
> >>
> >> I'm working on a patch that changes it now, based on code from John.
> >> It will introduce a new weave based format and change the in-
> >> development knit format so that characters disallowed by windows are
> >> quoted like in urls.
> >
> > Do we need to worry about the weave format at all? Why not just change
> > the knit format
> 
> I think it's at least possible that weaves will work better for some  
> users/uses, and so letting them handle all file-ids on Windows is  
> worthwhile.

Well, up to you. FWIW though - as we currently use them there are many
pathological cases, and once we have a knit plan_merge - I would
consider all weaves deprecated.

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: 191 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060411/d8e40f3c/attachment.pgp