From: Junio C Hamano <junkio@cox.net>
To: Jeff Garzik <jeff@garzik.org>
Cc: Git Mailing List <git@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: kernel cherry UN-picking?
Date: Fri, 11 May 2007 15:11:35 -0700 [thread overview]
Message-ID: <7v7irf9fjc.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7vbqgr9fn9.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Fri, 11 May 2007 15:09:14 -0700")
Junio C Hamano <junkio@cox.net> writes:
> Suppose you have something like this (you may have more than one
> such merge but the principle is the same):
>
> U---o---o---o---M---x---o---o---o---T
> /
> Linville o---o
>
> Up to 'U' you have already sent upstream and no need for
> resending. 'M' is merge with Linville tree. 'x' is the bad
> one, and 'o' are good ones. 'T' is the tip of your net driver
> branch.
>
> First find out 'x'. Then
>
> git format-patch -o ./outdir x..T
>
> would format everything starting from (but excluding) 'x' up to
> 'T'.
>
> Then
>
> git reset --hard x^
> git am ./outdir/*.patch
>
> would rebuild:
>
> U---o---o---o---M---x---o'--o'--o'--T'
> /
> Linville o---o
Correction. This would rebuild:
U---o---o---o---M-------o'--o'--o'--T'
/
Linville o---o
as if 'x' did not happen.
next prev parent reply other threads:[~2007-05-11 22:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 21:31 kernel cherry UN-picking? Jeff Garzik
2007-05-11 21:55 ` Andrew Morton
2007-05-11 21:56 ` Jeff Garzik
2007-05-15 2:39 ` Josef Sipek
2007-05-11 21:56 ` Junio C Hamano
2007-05-11 22:09 ` Junio C Hamano
2007-05-11 22:11 ` Junio C Hamano [this message]
2007-05-12 13:39 ` Jan Harkes
2007-05-12 14:01 ` Jan Harkes
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=7v7irf9fjc.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=akpm@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=jeff@garzik.org \
--cc=torvalds@linux-foundation.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 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.