bfiles filename encoding

Adrian Buehlmann adrian at cadifra.com
Mon Jun 7 10:47:01 CDT 2010


On 07.06.2010 17:27, Benjamin Pollack wrote:
> On Jun 7, 2010, at 9:52 AM, Adrian Buehlmann wrote:
> 
>>
>>> Perhaps we should cook up a new filename encoding algorithm for
>>> bfiles.  If it works, we could even propose it for core Mercurial once
>>> people have the appetite for yet another change there.
>>
>> Matt was against doing another repo format change just to work around
>> issue1713.
> 
> Is this harder than just using the hex encoding for spaces at the beginning of the string? What if we simply always used the hex encoding everywhere in the filename for spaces? The only drawback I see is that Windows users are more likely to go the non-reversible encoding route in their store directory.
> 

The hard thing is that any fix for issue1713 will need a new repo
format, i.e. a new entry in .hg/requires, with all consequences.

Finding a viable encoding then shouldn't be such a problem.

Simply encoding every space to '~20' would certainly do.



More information about the Mercurial-devel mailing list