[PATCH 1 of 5 V2] bundle2: very first version of a bundle2 bundler

Matt Mackall mpm at selenic.com
Thu Mar 20 17:08:34 CDT 2014


On Thu, 2014-03-20 at 11:39 -0700, pierre-yves.david at ens-lyon.org wrote:
> # HG changeset patch
> # User Pierre-Yves David <pierre-yves.david at fb.com>
> # Date 1395176450 25200
> #      Tue Mar 18 14:00:50 2014 -0700
> # Node ID 14623bafac62835e44ee4dee806978e1fd50540b
> # Parent  29b159bd71bc68e9868c5d2d748ab166dc7a5287
> bundle2: very first version of a bundle2 bundler

The big question I have from looking at this is how does it fit into the
existing framework? There is basically no similarity between these
classes and the existing bundle10/unbundle10 classes (which really
strongly suggest a naming scheme you ought to be using for your new
classes, no?) that I would expect them to eventually be
duck-type-compatible with.

At the end of the day, we need to reach a state where most code in the
push/pull path doesn't need to know or care if it's working with a
bundle10 or later object.

-- 
Mathematics is the supreme nostalgia of our time.




More information about the Mercurial-devel mailing list