From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: Jacob Keller <jacob.e.keller@intel.com>,
git@vger.kernel.org, Phillip Wood <phillip.wood@dunelm.org.uk>,
Jacob Keller <jacob.keller@gmail.com>
Subject: Re: [PATCH v2] fix cherry-pick/revert status when doing multiple commits
Date: Wed, 28 Jun 2023 09:26:19 -0700 [thread overview]
Message-ID: <xmqqfs6beeok.fsf@gitster.g> (raw)
In-Reply-To: <743b17ee-2c5b-be7e-70f3-76d0f9d0ff5e@gmail.com> (Phillip Wood's message of "Wed, 28 Jun 2023 12:11:03 +0100")
Phillip Wood <phillip.wood123@gmail.com> writes:
> Hi Jacob
>
> This version looks good to me
>
> Thanks for re-rolling
>
> Phillip
Thanks Jacob for writing and Phillip for reviewing. Queued.
prev parent reply other threads:[~2023-06-28 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 22:41 [PATCH v2] fix cherry-pick/revert status when doing multiple commits Jacob Keller
2023-06-28 11:11 ` Phillip Wood
2023-06-28 16:26 ` Junio C Hamano [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=xmqqfs6beeok.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=jacob.keller@gmail.com \
--cc=phillip.wood123@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
/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).