Possibly changing the path encoding format

Matt Mackall mpm at selenic.com
Thu Sep 13 00:28:55 CDT 2012


On Wed, 2012-09-12 at 23:21 +0200, Adrian Buehlmann wrote:
> On 2012-09-12 22:11, Bryan O'Sullivan wrote:
> > On Wed, Sep 12, 2012 at 12:28 PM, Adrian Buehlmann <adrian at cadifra.com
> > <mailto: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
> >     are.
> > 
> > 
> > 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.
> 
> Agreed. It's clear that we can't drop any encoding in use.
>
> However, the thing is, this will probably be the very last chance to
> jump on a repo format change bandwagon (provided we get the ok from Matt
> for a new repo format at all).

I'm ok with it, but I think we should beat the bushes to make sure we've
really, finally thought of everything.

-- 
Mathematics is the supreme nostalgia of our time.




More information about the Mercurial-devel mailing list