From: Jacob Keller <jacob.e.keller@intel.com>
To: <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Jacob Keller <jacob.keller@gmail.com>,
Glen Choo <chooglen@google.com>
Subject: Re: [PATCH] blame: use different author name for fake commit generated by --contents
Date: Mon, 24 Apr 2023 12:36:16 -0700 [thread overview]
Message-ID: <c4a99e9c-46c5-31fe-5004-2d741a5bc8a0@intel.com> (raw)
In-Reply-To: <20230424193508.2245566-1-jacob.e.keller@intel.com>
On 4/24/2023 12:35 PM, Jacob Keller wrote:
> From: Jacob Keller <jacob.keller@gmail.com>
>
Apologies but I forgot to add -v2 when formatting this patch, so the
subject really should be [PATCH v2].
Thanks,
Jake
next prev parent reply other threads:[~2023-04-24 19:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 19:35 [PATCH] blame: use different author name for fake commit generated by --contents Jacob Keller
2023-04-24 19:36 ` Jacob Keller [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-21 22:30 Jacob Keller
2023-04-21 23:34 ` Junio C Hamano
2023-04-22 0:11 ` Jacob Keller
2023-04-24 16:05 ` Junio C Hamano
2023-04-24 17:59 ` Glen Choo
2023-04-24 18:37 ` Jacob Keller
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=c4a99e9c-46c5-31fe-5004-2d741a5bc8a0@intel.com \
--to=jacob.e.keller@intel.com \
--cc=chooglen@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.keller@gmail.com \
/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).