[PATCH 5 of 5 RFC] obsolete: store obsolete revisions to cache file

[Augie Fackler]

On Thu, Oct 01, 2015 at 12:20:57AM +0900, Yuya Nishihara wrote:
> On Tue, 29 Sep 2015 17:04:04 -0500, Matt Mackall wrote:
> > On Fri, 2015-09-25 at 00:10 +0900, Yuya Nishihara wrote:
> > > On Wed, 23 Sep 2015 01:40:12 -0700, Pierre-Yves David wrote:
> > I'd prefer to always store big-endian. Endian-conversion is cheap and
> > intentionally choosing big-endian means we're slightly more likely to
> > get portability right when developing on x86 because we eliminate the
> > write-native-read-big or write-big-read-native cases without needing to
> > test on ARM/etc.
>
> Hmm, makes sense. Endian-conversion won't be slower than creating a Python
> int. Also, x86 provides bswap instruction if we really need it.

+1.

>
> OT: ARM is typically used in little-endian mode. I think well-known big-
> endian microprocessor is Atmel AVR?

The one I'm most familiar with is POWER and PowerPC, though POWER8
adds enough support that you can run it in little-endian mode.

> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> https://selenic.com/mailman/listinfo/mercurial-devel