From: Andrea Arcangeli <andrea@suse.de>
To: Shawn <core@enodev.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: constant Bitkeeper bitching
Date: Sun, 16 Mar 2003 23:46:43 +0100 [thread overview]
Message-ID: <20030316224643.GB1252@dualathlon.random> (raw)
In-Reply-To: <1047837820.3966.8.camel@localhost.localdomain>
On Sun, Mar 16, 2003 at 12:03:40PM -0600, Shawn wrote:
> [..] You had
> patches, folks... [..]
I agree with the rest but note that the above argument is silly too.
Patches are missing a great deal of info. bitkeeper is more useful for a
reason. Until today we had an information-loss problem, that was fixed
only for a restricted number of people for the last year, so it was very
far from a solution from my point of view. Today thanks to the kernel
CVS that Larry thankfully provided, IMHO this is finally solved and I
greatly appreciate that.
Of course if you don't develop the kernel you can live fine with
monolithic undocumented patches, you're not going to audit those diffs
anyways, do you? Few people will appreciate the difference between
patches and bk, but for developers having the finer granularity helps a
lot, so saying "go back to patches" is a no-way. Just try to extract
stuff from the -ac tree and you get the idea, I'm stunned how can Alan
submit stuff to Marcelo and Linus w/o major pain and leftovers (ok, some
are driver changes and they're easy to extract, but not everything is
that simple and self contained).
Andrea
next prev parent reply other threads:[~2003-03-16 22:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-16 18:03 constant Bitkeeper bitching Shawn
2003-03-16 22:46 ` Andrea Arcangeli [this message]
2003-03-16 23:26 ` Shawn
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=20030316224643.GB1252@dualathlon.random \
--to=andrea@suse.de \
--cc=core@enodev.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox