From: Andreas Schwab <schwab@linux-m68k.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: ding@gnus.org
Subject: Re: Using "git am" from Gnus
Date: Thu, 02 Apr 2015 20:39:50 +0200 [thread overview]
Message-ID: <877ftuv0g9.fsf@igel.home> (raw)
In-Reply-To: <jwv7ftv2r38.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 01 Apr 2015 22:41:05 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Ideally, I should be able to just select all the relevant email in the
> *Summary* buffer, indicate where is the Git tree to which those patches
> should be applied, and then let the command do its magic (which might
> include re-ordering the emails).
Process mark the mails in the right order (probably sorting by subject
first), pipe them to git am.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2015-04-02 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 2:41 Stefan Monnier
2015-04-02 18:39 ` Andreas Schwab [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=877ftuv0g9.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=ding@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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;
as well as URLs for NNTP newsgroup(s).