From: Larry McVoy <lm@bitmover.com>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: source control?
Date: Thu, 23 Aug 2001 15:49:47 -0700 [thread overview]
Message-ID: <20010823154947.X25998@work.bitmover.com> (raw)
In-Reply-To: <4148FEAAD879D311AC5700A0C969E89006CDE0A4@orsmsx35.jf.intel.com>
In-Reply-To: <4148FEAAD879D311AC5700A0C969E89006CDE0A4@orsmsx35.jf.intel.com>; from andrew.grover@intel.com on Thu, Aug 23, 2001 at 02:29:18PM -0700
On Thu, Aug 23, 2001 at 02:29:18PM -0700, Grover, Andrew wrote:
> Is Linux development ever going to use source control?
>
> This was talked about at the Kernel Summit, and I haven't heard anything
> about it since.
There are two features that Linus wants in BitKeeper that we haven't
finished yet. One is the removal of the revision control files from
the working tree and the other is the ability to break the tree up
into logical units (we call 'em filesets) so that you can more easily
pick and choose which patches you want in your tree.
Linus pinged me about these a while back, we've made some progress on
them but they aren't done yet. When they are done we'll let Linus take
it for a whirl and see what he thinks.
In the meantime, the PPC people maintain a pure Linux tree in BK, you
can see it at http://ppc.bkbits.net and Ted Tso has recently done a
nice import of the various kernel versions complete with Linus' change
logs. I need to work with the PPC guys and Ted to get to one tree;
it's not an easy issue because the PPC have a lot of changes in their
tree but Ted's tree was done more nicely, he did some extra work to
preserve timestamps and comments.
And to avoid yet-another-BK-flamewar, I'm not saying Linus will or will
not use BitKeeper, all I'm saying is that we're making changes he wants
and then he'll see if it is good enough for him. I will say that he has
eased slightly off of his original position of "I'll use BitKeeper when
it is the best" because I asked him if that meant what I think both he
and I would mean, i.e., "it is not physically possible for it to be better"
as opposed to "it's better than all the other crap out there". I think
we agreed we have to be well past #2 but not necessarily to #1 (which is
a good thing, at the rate we're going we'll hit the best sometime this
century but that's as close as I want to call it :-)
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2001-08-23 22:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-23 21:29 source control? Grover, Andrew
2001-08-23 22:34 ` Nicholas Knight
2001-08-23 22:49 ` Larry McVoy [this message]
2001-08-23 23:28 ` Alan Cox
2001-08-24 3:22 ` Cort Dougan
2001-08-24 17:02 ` Florian Weimer
2001-08-24 10:29 ` Gérard Roudier
2001-08-24 12:16 ` Alan Cox
2001-08-24 13:15 ` Gérard Roudier
-- strict thread matches above, loose matches on Subject: below --
2001-08-24 12:53 Samium Gromoff
2001-08-24 13:25 Samium Gromoff
2001-08-24 17:20 Samium Gromoff
2001-08-24 17:25 ` Larry McVoy
2001-08-24 17:29 ` Florian Weimer
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=20010823154947.X25998@work.bitmover.com \
--to=lm@bitmover.com \
--cc=andrew.grover@intel.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