mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
	Linux-Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: BK Kernel Hacking HOWTO
Date: Tue, 26 Feb 2002 11:34:02 -0700	[thread overview]
Message-ID: <20020226113402.K12832@lynx.adilger.int> (raw)
In-Reply-To: <3C751CB2.52110E58@mandrakesoft.com> <Pine.GSO.4.21.0202261842290.8085-100000@vervain.sonytel.be>
In-Reply-To: <Pine.GSO.4.21.0202261842290.8085-100000@vervain.sonytel.be>; from geert@linux-m68k.org on Tue, Feb 26, 2002 at 06:45:08PM +0100

On Feb 26, 2002  18:45 +0100, Geert Uytterhoeven wrote:
> So what if Linus isn't happy with the changes you made in the for-Him-to-pull
> tree? How do I back off (part of the changes)?

Well, assuming he tells you that there is a problem, run "bk undo -r <rev>.."
to remove the patchset that he doesn't like (in theory).  If there have been
a large number of changes after <rev> then they are all removed (there is no
way to remove only a single CSET from within the middle of the tree.  Then
you re-do the changes in a way that Linus likes, and submit a new CSET.

You could also add the fix to the same tree and hope he accepts both CSETs,
but I think Linus doesn't want to clutter up his tree with <patch>+<fix>
instead of a single <patch> that was correct in the first place.

In some cases, you are probably better off to export the changes in <rev>
into a diff, get a new Linus BK tree, and re-apply the patches + fixes
and generate a new CSET from that.

Not perfect, but that's life.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2002-02-26 18:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21 16:13 Jeff Garzik
2002-02-21 16:31 ` Jeff Garzik
2002-02-21 16:40 ` Stelian Pop
2002-02-21 18:40   ` Andreas Dilger
2002-02-22 11:44     ` Stelian Pop
2002-02-26 17:45 ` Geert Uytterhoeven
2002-02-26 18:34   ` Andreas Dilger [this message]
2002-02-26 20:19     ` Geert Uytterhoeven
2002-02-26 20:29       ` Larry McVoy
2002-02-26 20:40         ` Geert Uytterhoeven
2002-02-26 20:57       ` Andreas Dilger
2002-02-21 16:54 willy tarreau

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=20020226113402.K12832@lynx.adilger.int \
    --to=adilger@turbolabs.com \
    --cc=geert@linux-m68k.org \
    --cc=jgarzik@mandrakesoft.com \
    --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®