On Sun, Aug 21, 2005 at 14:14:54 +0200, Matthieu Moy wrote: > Martin Langhoff <[EMAIL PROTECTED]> writes: > > > This transition is tainted by the fact that patch-centric SCMs have > > disappointed me a bit. > > FYI, Arch 2.0 (which is probably dead before being finished) is not > patch-centric, but snapshot-based, like GIT is. Bazaar-NG will use > weaves as the storage format.
And what about Bazaar-NG and changesets? Will the merge in bazaar-ng store just the collapsed patch (as arch/bazaar do) or the constituents and a resolution (as git and mercurial do)? I believe the later is better for further merges (you may need the constituents and may not be able to access other repositories) and, as a side-efect, provides all the important semantics of git and mercurial (well, mercurial has one additional feature of allowing multiple heads at any given time (which git also can do, but needs explicit names for them)). Note: I have tried to find the answer on the web (http://www.bazaar-ng.org/), but it wasn't clear to me. From http://bazaar-ng.org/doc/merge.html is seems more like the first option (storing as one big merger), but that is from the "obsolete" documentation. ------------------------------------------------------------------------------- Jan 'Bulb' Hudec <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
_______________________________________________ Gnu-arch-users mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/
