public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Dave Jones <davej@suse.de>,
	Linus Torvalds <torvalds@transmeta.com>,
	Larry McVoy <lm@bitmover.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.5.8-pre1
Date: Sat, 6 Apr 2002 09:05:40 -0800	[thread overview]
Message-ID: <20020406090540.B12017@work.bitmover.com> (raw)
In-Reply-To: <20020404223425.K11833@suse.de> <20020403195445.U17549@work.bitmover.com> <Pine.LNX.4.33.0204041203440.14206-100000@penguin.transmeta.com> <20020404223425.K11833@suse.de> <22175.1018107407@redhat.com>

On Sat, Apr 06, 2002 at 04:36:47PM +0100, David Woodhouse wrote:
> 
> davej@suse.de said:
> > With Marcelo using bk these days, is it possible that you can cherry
> > pick certain csets from his bk tree ?
> 
> I couldn't work out how to make BK even attempt that. 
> 
> If you commit harmless and irrelevant changeset 'X' to a repository, then 
> commit a completely separate changeset 'Y' which doesn't touch any of the 
> same files, then it seems to be impossible¹ to import 'Y' into a different 
> tree without also importing 'X'.

If you want to do it preserving all the BK info, i.e., a pull with some
option to send a particular changeset, that doesn't work.  BK has an 
invariant which is that the parent of any changeset you send must be
present in the receiving repository or it won't work.

What you want to do is cherrypick, to do that with BK you have two choices:
    a) wait for LODs
    b) export as a patch and import as a patch.
The second one works fine but causes problems over the long run, especially
with file creates.
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  reply	other threads:[~2002-04-06 17:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-04  1:22 Linux-2.5.8-pre1 Linus Torvalds
2002-04-04  3:46 ` Linux-2.5.8-pre1 Larry McVoy
2002-04-04  3:54   ` Linux-2.5.8-pre1 Larry McVoy
2002-04-04 20:12     ` Linux-2.5.8-pre1 Linus Torvalds
2002-04-04 20:18       ` Linux-2.5.8-pre1 Larry McVoy
2002-04-04 20:34       ` Linux-2.5.8-pre1 Dave Jones
2002-04-06 15:36         ` Linux-2.5.8-pre1 David Woodhouse
2002-04-06 17:05           ` Larry McVoy [this message]
2002-04-06 17:25             ` Linux-2.5.8-pre1 David Woodhouse
2002-04-06 17:30               ` Linux-2.5.8-pre1 Larry McVoy
2002-04-06 19:14                 ` Linux-2.5.8-pre1 David Woodhouse
2002-04-04 10:19 ` Linux-2.5.8-pre1 Martin Dalecki
2002-04-04 11:45   ` Linux-2.5.8-pre1 Tim Schmielau
2002-04-04 10:49     ` Linux-2.5.8-pre1 Martin Dalecki
2002-04-05  6:02       ` [patch] Linux-2.5.8-pre1 Tim Schmielau
2002-04-04 12:05     ` Linux-2.5.8-pre1 Dave Jones
2002-04-04 15:45   ` IDE/SUPPORT_VLB_SYNC in 2.5.x Geert Uytterhoeven
2002-04-04 14:52     ` Martin Dalecki
2002-04-05  8:26       ` Geert Uytterhoeven
2002-04-04 11:55 ` Linux-2.5.8-pre1 fs/dquot Martin Dalecki
2002-04-04 16:43   ` Alexander Viro
2002-04-04 15:50     ` Martin Dalecki
2002-04-04 22:52 ` Linux-2.5.8-pre1 Mike Fedyk

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=20020406090540.B12017@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=davej@suse.de \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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