bad characters in filenames on windows

Martin Pool mbp at sourcefrog.net
Tue Apr 11 03:24:08 BST 2006


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.

-- 
Martin







More information about the bazaar mailing list