[haiku-development] Re: VOTE: Git or Mercurial (hg) as Haiku's new source control tool

  • From: Sean Healy <jalopeura@xxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Sat, 14 May 2011 06:43:34 +0100

On 13-May-11 23:06, Oliver Tappe wrote:

On 2011-05-13 at 23:28:07 [+0200], Andreas Färber<andreas.faerber@xxxxxx>

For some time I've worked with Git and Mercurial in parallel and I
personally found Git more convenient to handle.
I wouldn't mind staying with SVN and using the official Git mirror

You mean with a then writable Git mirror? Or how else would you push
commits to subversion?

I know it's possible to keep repos in sync [1], but wouldn't that cause a lot of issues?

1) Developers on different repos - what would that do to bug tracking? (Although I suppose we could turn off SVN for everyone except the sync script and just use it for nightly builds and alpha releases.)

2) We'd need some way to easily turn those official SVN revision numbers (from bug reports, for example) into git hashes so developers could find the branch in question. (I suppose we could keep a file in the SVN repo with the corresponding hash.)

3) What kind of performance would synching have on a repo the size of Haiku's? (I don't think simply updating once a day would work; the SVN revision numbers would have a whole day's worth of changesets in them, and that would be less useful for finding problems.)

[1] http://www.icoretech.org/2009/08/how-to-mirror-a-svn-repository-on-github/

Other related posts: