From: Lars Marowsky-Bree <lmb@suse.de>
To: Larry McVoy <lm@work.bitmover.com>,
Roger Gammans <roger@computer-surgery.co.uk>,
linux-kernel@vger.kernel.org
Subject: Re: using bitkeeper to backport subsystems?
Date: Tue, 23 Jul 2002 10:16:15 +0200 [thread overview]
Message-ID: <20020723081615.GB1176@marowsky-bree.de> (raw)
In-Reply-To: <20020722154443.E19057@work.bitmover.com>
On 2002-07-22T15:44:43,
Larry McVoy <lm@bitmover.com> said:
> > With all due respect to Larry and the bk team, I think you'll
> > find determining 'needed changesets' in this case is a _hard_ problem.
> Thanks, we agree completely. It's actually an impossible problem
> for a program since it requires semantic knowledge of the content
> under revision control.
So, another option would be to have the developer define explicit dependencies
for his changesets, but I fear that might prove to cumbersome, too.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
Immortality is an adequate definition of high availability for me.
--- Gregory F. Pfister
next prev parent reply other threads:[~2002-07-23 8:20 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 [this message]
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=20020723081615.GB1176@marowsky-bree.de \
--to=lmb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@work.bitmover.com \
--cc=roger@computer-surgery.co.uk \
/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®