unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jani Nikula <jani@nikula.org>
To: Matt Armstrong <marmstrong@google.com>
Cc: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: Notmuch dev workflow: applying patches to local trees
Date: Tue, 8 Nov 2016 11:15:47 +0200	[thread overview]
Message-ID: <CAB+hUn94QuS2EfyPmo-qZOwVcbUDzHW-dpdv_UFnL-_QZgFoGA@mail.gmail.com> (raw)
In-Reply-To: <qf5y40uhoe4.fsf@marmstrong-linux.kir.corp.google.com>

On Tue, Nov 8, 2016 at 1:16 AM, Matt Armstrong <marmstrong@google.com> wrote:
> I'm not experienced with managing patches via email on this list,
> especially when it comes to applying patches sent out for review and
> testing.  Is there a documented best practice?

Not sure about best practice, but this works for me:

M-x cd RET /path/to/repo RET

Apply a single patch in show mode:
| git am RET

Apply all expanded patch messages in a thread in show mode:
C-u | git am RET

You do have to setup the branch yourself in advance.

> Ideally, I'd like a "dwim" command that does something reasonable, such
> as take messages from the current thread and apply the patch series to a
> new/pristine git branch in my local repo.

You can also write your own shell script that does the right things
when you pipe patch(es) to it.

BR,
Jani.

  reply	other threads:[~2016-11-08  9:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07 23:16 Notmuch dev workflow: applying patches to local trees Matt Armstrong
2016-11-08  9:15 ` Jani Nikula [this message]
2016-11-08 19:19   ` Matt Armstrong

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=CAB+hUn94QuS2EfyPmo-qZOwVcbUDzHW-dpdv_UFnL-_QZgFoGA@mail.gmail.com \
    --to=jani@nikula.org \
    --cc=marmstrong@google.com \
    --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).