From: Jameson Rollins <jrollins@finestructure.net>
To: notmuch@notmuchmail.org
Subject: Re: Handling PATCH from notmuchmail
Date: Tue, 23 Nov 2010 10:44:39 -0500 [thread overview]
Message-ID: <87oc9g3uzc.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87mxp0nlkx.fsf@SSpaeth.de>
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
On Tue, 23 Nov 2010 15:47:26 +0100, Sebastian Spaeth <Sebastian@SSpaeth.de> wrote:
> On Mon, 22 Nov 2010 22:49:15 +0100, Xavier Maillard <xma@gnu.org> wrote:
> > out of curiosity, how hackers on this mailing list and using notmuch
> > (through GNU Emacs client if at all) do handle all the patches sent here
>
> cF to stash the filename and
> then switch to shell and do
> git am -3 ctrl-shift-v RET
notmuch show --format=mbox id:XXX | git am
works well too, as does
notmuch show --format=mbox thread:XXX | git am
for a whole series.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2010-11-23 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 21:49 Handling PATCH from notmuchmail Xavier Maillard
2010-11-23 14:47 ` Sebastian Spaeth
2010-11-23 15:44 ` Jameson Rollins [this message]
2010-11-23 15:41 ` Michal Sojka
2010-11-23 17:27 ` Jed Brown
2010-11-23 21:06 ` Xavier Maillard
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oc9g3uzc.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).