Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Kernel.org Tools" <tools@linux.kernel.org>,
	 Philippe Blain <levraiphilippeblain@gmail.com>
Subject: Re: [PATCH b4 0/2] am, shazam: allow cherry-picking an out-of-series patch
Date: Fri, 26 May 2023 14:28:52 -0400	[thread overview]
Message-ID: <168512573270.62751.10929456298761671390.b4-ty@linuxfoundation.org> (raw)
In-Reply-To: <20230415-am-cherry-pick-suggestion-v1-0-8951a2274256@gmail.com>


On Sat, 15 Apr 2023 15:30:58 -0400, Philippe Blain wrote:
> This series makes am and shazam able to cherry-pick a patch sent by a reviewer
> as a suggestion (second patch). The first patch is a preparatory
> simplification.
> 
> If you want to test it, you can do so in a clone of git.git:
> 
>     git clone https://github.com/gitgitgadget/git -b pr-1515/phil-blain/doc-auto-merge-v1
>     git checkout 66c7e51415
>     b4 am -o- -P_ https://lore.kernel.org/git/ZDnCMegeiw0kT5oj@nand.local/
> 
> [...]

Applied, thanks!

[1/2] mbox.py::make_am: simplify check for early return
      commit: 6c9ad4ec28f9a14cd8d20c933eef7bce0285a60a
[2/2] am, shazam: allow cherry-picking an out-of-series patch
      commit: 5872a3cfbb27a8511ee8a07f2b1a5bc79163dcd6

Best regards,
-- 
Konstantin Ryabitsev <konstantin@linuxfoundation.org>


      parent reply	other threads:[~2023-05-26 18:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-15 19:30 [PATCH b4 0/2] am, shazam: allow cherry-picking an out-of-series patch Philippe Blain
2023-04-15 19:30 ` [PATCH b4 1/2] mbox.py::make_am: simplify check for early return Philippe Blain
2023-04-15 19:31 ` [PATCH b4 2/2] am, shazam: allow cherry-picking an out-of-series patch Philippe Blain
2023-05-06 20:23 ` [PATCH b4 0/2] " Philippe Blain
2023-05-26 18:28 ` Konstantin Ryabitsev [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=168512573270.62751.10929456298761671390.b4-ty@linuxfoundation.org \
    --to=konstantin@linuxfoundation.org \
    --cc=levraiphilippeblain@gmail.com \
    --cc=tools@linux.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).