From: Tom Rini <trini@kernel.crashing.org>
To: Andreas Schuldei <andreas@schuldei.org>
Cc: Christoph Hellwig <hch@lst.de>, linux-kernel@vger.kernel.org
Subject: Re: using bitkeeper to backport subsystems?
Date: Mon, 22 Jul 2002 08:20:31 -0700 [thread overview]
Message-ID: <20020722152031.GB692@opus.bloom.county> (raw)
In-Reply-To: <20020722102705.GB21907@lukas>
On Mon, Jul 22, 2002 at 12:27:05PM +0200, Andreas Schuldei wrote:
> * Christoph Hellwig (hch@lst.de) [020722 10:29]:
> > On Mon, Jul 22, 2002 at 01:15:10AM -0600, Val Henson wrote:
> > > Sigh. I hate this question: "How will BitKeeper make it easier to
> > > port something between 2.4 and 2.5?" Answer: "Bk won't help - at
> > > least not as much as it would help if 2.5 had been cloned from 2.4."
> >
> > 2.5 _is_ cloned from 2.4..
>
> can one make use of that somehow?
Possibly, once bitkeeper allowes ChangeSets to only depend on what they
actually need, not every previous ChangeSet in the repository. IIRC,
this was one of the things Linus asked for, so hopefully it will happen.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2002-07-22 15:17 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 [this message]
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
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=20020722152031.GB692@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=andreas@schuldei.org \
--cc=hch@lst.de \
--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
all inboxes | Powered by JetHome®