[haiku-development] Re: Patch format (was: Commit-access for Matt Madia)
- From: Ingo Weinhold <ingo_weinhold@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 28 Feb 2010 12:58:28 +0100
On 2010-02-28 at 11:07:28 [+0100], Andreas Färber <andreas.faerber@xxxxxx>
wrote:
> Am 27.02.2010 um 22:58 schrieb Ryan Leavengood:
> > On Sat, Feb 27, 2010 at 4:32 PM, Ingo Weinhold
> > <ingo_weinhold@xxxxxx> wrote:
> >>
> >> Thanks for the explanation. Unfortunately svn doesn't help with
> >> this at all
> >> (AFAIK). I believe mercurial would, though.
> >
> > Or obviously Git, but it seems many Haiku developers are not fans of
> > Git for whatever reason. I'd certainly consider using Mercurial though
> > if we ever wanted to switch to a distributed version control system
> > (which I think could be useful.)
>
> I would think the issue is that Subversion has been around longer and
> more people know its command line options. Git, Mercurial and Bazaar
> (to mention that one as well) would all be new.
> 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. E.g. our read-only mercurial repository at
http://hg.haiku-os.org/haiku/haiku-trunk has the complete history.
> 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.
> What's the status of Mercurial on Haiku?
I've managed to check out the OpenJDK Haiku repository a few days ago
(though with a hang at the first attempt, which is something one sometimes
also sees with svn), and from his blog Andrew Bachmann did so under alpha 1
already. So I'd say it has been working well enough for a while.
> Last time I tried, it didn't
> work due to #2072 (Perl's socket.pm).
Isn't mercurial written in python?
> Has that been resolved?
The ticket is still open and no one seemed to have looked into it actively.
Unless someone fixed the problem unknowingly, it still exists.
> It's
> needed for the Java port iirc.
> 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.
CU, Ingo
Other related posts:
