[haiku-development] Re: Patch format (was: Commit-access for Matt Madia)

  • From: Andreas Färber <andreas.faerber@xxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Sun, 28 Feb 2010 18:12:28 +0100


Am 28.02.2010 um 12:58 schrieb Ingo Weinhold:

On 2010-02-28 at 11:07:28 [+0100], Andreas Färber <andreas.faerber@xxxxxx >
wrote:
To my knowledge and past experience, Git used to be the most suited
for tracking an SVN repository - personally or for a future switch -
whereas Mercurial only imported single snapshots rather than the
complete SVN history.

You are mistaken.

Or maybe I just followed the wrong tutorial, say, two years ago. The Mercurial website has improved since then, so probably the tools and tutorials have as well.

E.g. our read-only mercurial repository at
http://hg.haiku-os.org/haiku/haiku-trunk has the complete history.

Now that's cool! Is this updated by SVN commit hooks or periodically? I didn't find mention of this on the website.


Another part of the problem will be that the project layout is
tailored to SVN, with lots of relatively independent components
sitting in a huge tree. That way it's hard to find a free repository
host, whether for personal branches like my signal stuff (btw, @Ingo
thanks for the POSIX hint! still struggling...) or the official thing
(1 GB minus the checked out files for r35495 with git-svn).

That's indeed a problem, if you want to host the repository somewhere. For
local work the size shouldn't be that much of an issue.

I consider the ability to easily remote-host copies of my work a significant advantage of distributed VCSs. A number of ports would've been lost through KDLs otherwise. ;)

Isn't mercurial written in python?

Yeah, I already corrected myself after poking at 1.4.3. Probably mixed that up with SVK.

[Mercurial]
Git is C-based and has little dependencies.
Bazaar was a little more complicated due to Python bootstrapping, but
appeared to work after Axel resolved the BFS issues uncovered by it.
But similar tool problems probably still apply to svn itself, not
having heard of an upstream merger of the apr and subversion patches?

Indeed there still seem to be networking issues.

I was rather referring to ease of building the tools yourself, which is what I mostly do. If you provide Optional Packages, then for most other people it becomes irrelevant.

Andreas

Other related posts: