From: Christoph Hellwig <hch@lst.de>
To: Mark Mielke <mark@mark.mielke.cc>
Cc: 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 15:48:11 +0200 [thread overview]
Message-ID: <20020722154811.A19085@lst.de> (raw)
In-Reply-To: <20020722094505.A20319@mark.mielke.cc>; from mark@mark.mielke.cc on Mon, Jul 22, 2002 at 09:45:05AM -0400
On Mon, Jul 22, 2002 at 09:45:05AM -0400, Mark Mielke wrote:
> 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)
Just that there were no official 2.2/2.3 Linux BK trees..
next prev parent reply other threads:[~2002-07-22 13:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-21 23:34 using bitkeeper to backport subsystems? 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
2002-07-22 13:48 ` Christoph Hellwig [this message]
2002-07-22 17:52 ` Val Henson
-- strict thread matches above, loose matches on Subject: below --
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=20020722154811.A19085@lst.de \
--to=hch@lst.de \
--cc=andreas@schuldei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mark.mielke.cc \
--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