From: Mark Mielke <mark@mark.mielke.cc>
To: Christoph Hellwig <hch@lst.de>,
Thunder from the hill <thunder@ngforever.de>,
Val Henson <val@nmt.edu>, Andreas Schuldei <andreas@schuldei.org>,
linux-kernel@vger.kernel.org
Subject: Re: using bitkeeper to backport subsystems?
Date: Mon, 22 Jul 2002 09:45:05 -0400 [thread overview]
Message-ID: <20020722094505.A20319@mark.mielke.cc> (raw)
In-Reply-To: <20020722124627.A16636@lst.de>; from hch@lst.de on Mon, Jul 22, 2002 at 12:46:27PM +0200
On Mon, Jul 22, 2002 at 12:46:27PM +0200, Christoph Hellwig wrote:
> On Mon, Jul 22, 2002 at 04:43:58AM -0600, Thunder from the hill wrote:
> > On Mon, 22 Jul 2002, Christoph Hellwig wrote:
> > > 2.5 _is_ cloned from 2.4..
> > Not exactly.
> Yes, _exactly_. With BK trees are either cloned or completly separate.
It would have been very foolish to not clone 2.4. Worst case would have
2.5 cloned from 2.3 or 2.2, but the version tree would still be intact,
just a little indirect. (As far as I am aware, 2.5 is cloned from 2.4)
> > Several things have been moved around, note e.g. the
> > additional "sound" directory...
> What does the movearound of files/directories change?
Nothing, assuming BK is a proper soure management system, which it should be.
In CVS? It would be big problems. But this is one reason why CVS is not
used for real projects such as the Linux Kernel.
mark
--
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
next prev parent reply other threads:[~2002-07-22 13:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-21 23:34 Andreas Schuldei
2002-07-22 7:15 ` Val Henson
2002-07-22 8:29 ` Christoph Hellwig
2002-07-22 10:27 ` Andreas Schuldei
2002-07-22 10:29 ` Christoph Hellwig
2002-07-22 15:25 ` Larry McVoy
2002-07-25 21:48 ` Andreas Schuldei
2002-07-22 15:20 ` Tom Rini
2002-07-22 22:29 ` Roger Gammans
2002-07-22 22:44 ` Larry McVoy
2002-07-23 8:16 ` Lars Marowsky-Bree
2002-07-23 18:38 ` Eric W. Biederman
2002-07-23 22:46 ` Larry McVoy
2002-07-22 10:43 ` Thunder from the hill
2002-07-22 10:46 ` Christoph Hellwig
2002-07-22 11:02 ` Thunder from the hill
2002-07-22 11:03 ` Christoph Hellwig
2002-07-22 13:45 ` Mark Mielke [this message]
2002-07-22 13:48 ` Christoph Hellwig
2002-07-22 17:52 ` Val Henson
2002-07-23 14:31 Matthias Urlichs
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=20020722094505.A20319@mark.mielke.cc \
--to=mark@mark.mielke.cc \
--cc=andreas@schuldei.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder@ngforever.de \
--cc=val@nmt.edu \
/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
all inboxes | Powered by JetHome®