From: Michael Radziej <mir@noris.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Alex Riesen <raa.lkml@gmail.com>, Miles Bader <miles@gnu.org>,
git@vger.kernel.org
Subject: Re: multiple-commit cherry-pick?
Date: Fri, 7 Nov 2008 11:46:30 +0100 [thread overview]
Message-ID: <20081107104630.GB12424@noris.de> (raw)
In-Reply-To: <7vskq4gmf5.fsf@gitster.siamese.dyndns.org>
On Thu, Nov 06, Junio C Hamano wrote:
> Or "git show --pretty=email $commit1 $commit2" ... piped to "am"?
Or make git show write shell commands.
I often have commits that later need to be cherry-picked into other
branches. For these, I use a commit message that starts with the name of the
branch, like "implement-foo: make foo barfy". Later when I want to do the
cherry-picking, I use this:
git log t/whatever..master --reverse --pretty=tformat:'git cherry-pick %h #
%s' | sed 's/^\([^:]*\) \([^:]*\):/git checkout \2 \&\& \1/'
giving me output like:
git checkout implement-foo && git cherry-pick 90ce727 # make foo barfy
git checkout ...
... and I'm ready for cut'n'paste.
Michael
--
noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg -
Tel +49-911-9352-0 - Fax +49-911-9352-100
http://www.noris.de - The IT-Outsourcing Company
Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel, Hansjochen Klenk -
Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689
prev parent reply other threads:[~2008-11-07 10:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 2:45 multiple-commit cherry-pick? Miles Bader
2008-11-06 3:24 ` Deskin Miller
2008-11-06 9:51 ` Björn Steinbrink
2008-11-06 12:14 ` Miles Bader
2008-11-06 12:26 ` Björn Steinbrink
2008-11-07 5:09 ` Miles Bader
2008-11-07 11:03 ` Björn Steinbrink
2008-11-07 11:46 ` Miles Bader
2008-11-06 21:37 ` Alex Riesen
2008-11-07 3:29 ` Linus Torvalds
2008-11-07 4:38 ` Miles Bader
2008-11-07 7:13 ` Alex Riesen
2008-11-07 5:00 ` Junio C Hamano
2008-11-07 7:12 ` Alex Riesen
2008-11-07 18:08 ` Linus Torvalds
2008-11-09 10:25 ` Alex Riesen
2008-11-10 19:58 ` Johannes Schindelin
2008-11-10 20:24 ` Alex Riesen
2008-11-10 21:31 ` Johannes Schindelin
2008-11-14 5:08 ` Chris Frey
2008-11-14 14:00 ` Johannes Schindelin
2008-11-14 16:11 ` Linus Torvalds
2008-11-14 16:59 ` Johannes Schindelin
2008-11-14 17:29 ` Junio C Hamano
2008-11-14 17:41 ` Linus Torvalds
2008-11-14 17:55 ` Linus Torvalds
2008-11-16 9:11 ` Pierre Habouzit
2008-11-14 18:38 ` Francis Galiegue
2008-11-10 20:41 ` Junio C Hamano
2008-11-10 21:34 ` Johannes Schindelin
2008-11-07 10:46 ` Michael Radziej [this message]
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=20081107104630.GB12424@noris.de \
--to=mir@noris.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=miles@gnu.org \
--cc=raa.lkml@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox