[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Re: Future of GNU Arch, bazaar and bazaar-ng ... ?

From: Jan Hudec
Subject: Re: [Gnu-arch-users] Re: Future of GNU Arch, bazaar and bazaar-ng ... ?
Date: Sun, 21 Aug 2005 15:10:42 +0200
User-agent: Mutt/1.5.10i

On Sun, Aug 21, 2005 at 14:14:54 +0200, Matthieu Moy wrote:
> Martin Langhoff <address@hidden> 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 (,
but it wasn't clear to me. From is seems
more like the first option (storing as one big merger), but that is from the
"obsolete" documentation.

                                                 Jan 'Bulb' Hudec 

Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]