From: Christoph Hellwig <hch@lst.de>
To: Thunder from the hill <thunder@ngforever.de>
Cc: 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 12:46:27 +0200 [thread overview]
Message-ID: <20020722124627.A16636@lst.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0207220443230.3309-100000@hawkeye.luckynet.adm>; from thunder@ngforever.de on Mon, Jul 22, 2002 at 04:43:58AM -0600
On Mon, Jul 22, 2002 at 04:43:58AM -0600, Thunder from the hill wrote:
> Hi,
>
> 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.
> Several things have been moved around, note e.g. the
> additional "sound" directory...
What does the movearound of files/directories change?
next prev parent reply other threads:[~2002-07-22 10:43 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 [this message]
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
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=20020722124627.A16636@lst.de \
--to=hch@lst.de \
--cc=andreas@schuldei.org \
--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 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.