[haiku-development] Re: merge branch

  • From: Niels Reedijk <niels.reedijk@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Wed, 19 May 2010 18:33:52 +0200

Hi,

On 19 May 2010 17:01, Andreas Färber <andreas.faerber@xxxxxx> wrote:
> Hi Niels,
>
> Am 18.05.2010 um 11:09 schrieb Niels Reedijk:
>
>> My next developer-tools project is going to be an hg<->svn bridge. I
>> hope to deliver a proof-of-concept soon (which would then also be
>> useful for a git<->svn bridge). The difference from hgsvn and
>> hgsubversion is that it is all done server-side, meaning the end user
>> does not have to bother with the logistics that it all involves.
>
> Is there really a need to do this for git?

Yes there is. All solutions depend on a personal git <-> svn
connection. This means that everybody is creating his own unique
repository, with unique changeset ids. That means that between git
trees the changesets cannot be exchanged, which takes away one of the
advantages of a distributed system.

When this svn<->git/hg bridge is implemented at a central repository,
all changeset ids will be consistent, and as such the free floating of
changesets (and the lovely issues of merging) is accomodated.

N>

Other related posts: