All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Miles Bader <miles@gnu.org>
Cc: Asfand Yar Qazi <ay0305@qazi.f2s.com>, linux-kernel@vger.kernel.org
Subject: Re: Why not GNU Arch instead of BitKeeper?
Date: Wed, 13 Apr 2005 14:07:00 +0100	[thread overview]
Message-ID: <20050413130700.GA12244@linux-mips.org> (raw)
In-Reply-To: <buo1x9f41zg.fsf@mctpc71.ucom.lsi.nec.co.jp>

On Wed, Apr 13, 2005 at 03:36:35PM +0900, Miles Bader wrote:

> Asfand Yar Qazi <ay0305@qazi.f2s.com> writes:
> > I'm surprised nobody considered GNU Arch 
> > (http://www.gnu.org/software/gnu-arch/) to replace BitKeeper - it was 
> > probably started in direct response to the Linux Kernel using a 
> > non-free tool.
> >
> > I must say I haven't used it, but from reviews and comparisons I've 
> > read, it seems to be a good tool.
> 
> I agree (I use it) -- but of course it has its own issues.  For instance
> it has a _lot_ less attention payed to optimization than one might wish
> (judging from "git", this is very important to Linus :-).  The concept
> of "archives" and their associated namespace offer some nice advantages,
> but is a very different model than BK uses, and I presume sticking with
> the familiar and simple BK model was attractive.

You can get somebody to be doing some work with bitkeeper within a few
minutes.  Arch has a much longer getting started phase.

  Ralf

      reply	other threads:[~2005-04-13 13:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13  6:17 Why not GNU Arch instead of BitKeeper? Asfand Yar Qazi
2005-04-13  6:36 ` Miles Bader
2005-04-13 13:07   ` Ralf Baechle [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050413130700.GA12244@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=ay0305@qazi.f2s.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.