[haiku-development] Re: Finally deciding on a new source control system for Haiku

  • From: Daniel Pihlström <threecreepio@xxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Mon, 2 May 2011 09:05:54 +0200

On Mon, May 2, 2011 at 8:29 AM, Niels Sascha Reedijk <
niels.reedijk@xxxxxxxxx> wrote:

> But most of the errors for hg were a file permission problem,
> indicating that either Haiku's file system, the POSIX part of Haiku,
> or Python's glue to Haiku, or the hg test suite has a flaw. (The
> latter is not unlikely because of the way the tests work).
> So in this sense it seems to me that the choice will be less 'clear'
> than envisioned. It really comes down to taste.
> Regards,
> N>
Sure, the whole argument is pretty much taste, as the actual tools are
similar enough to where it probably won't really matter which you choose
(assuming that Haiku supports them equally well.)

What's more interesting to me personally is the GitHub alternative. If the
barrier to entry entry for new developers is an issue, making use of their
fork + pull request process, in addition to just how widely used it is by
other projects, should at the very least be tempting.


Other related posts: