Possibly changing the path encoding format
bos at serpentine.com
Wed Sep 12 15:11:18 CDT 2012
On Wed, Sep 12, 2012 at 12:28 PM, Adrian Buehlmann <adrian at cadifra.com>wrote:
> I agree that my auxencode2 possibly wouldn't change much compared to
> current auxencode. But you could drop the logic around where the periods
In principle yes, but in practice the small reduction in C code would be
counterbalanced by introducing a new code path in Python, as we can't drop
the current fncache encoding stuff until the sun goes dark.
> Sounds good to me. I was actually hoping you would make a proposal in
I'd be happy to do the work to implement this, but this is one of those
rare cases where it's less work to describe the desired behaviour in
English than in code.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mercurial-devel