From: Junio C Hamano <gitster@pobox.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Michael Strawbridge" <michael.strawbridge@amd.com>,
"Luben Tuikov" <luben.tuikov@amd.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Emily Shaffer" <nasamuffin@google.com>,
"Doug Anderson" <dianders@chromium.org>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [REGRESSION] uninitialized value $address in git send-email
Date: Wed, 20 Sep 2023 08:43:24 -0700 [thread overview]
Message-ID: <xmqq7cokc0kj.fsf@gitster.g> (raw)
In-Reply-To: <ZQrQsa5GJEVhBttT@debian.me> (Bagas Sanjaya's message of "Wed, 20 Sep 2023 18:00:01 +0700")
Bagas Sanjaya <bagasdotme@gmail.com> writes:
> Originally, I was intended to report regression on handling multiple
> addresses passed in a single --to/--cc/--bcc option.
You refer to v2.40 and v2.41 in the message I am responding to, but
do you have a bisection? There seem to have been five topics around
send-email during that timeperiod.
$ git log --oneline --first-parent v2.40.0..v2.41.0 git-send-email.perl
b04671b638 Merge branch 'jc/send-email-pre-process-fix'
64477d20d7 Merge branch 'mc/send-email-header-cmd'
b6e9521956 Merge branch 'ms/send-email-feed-header-to-validate-hook'
c4c9d5586f Merge branch 'rj/send-email-validate-hook-count-messages'
647a2bb3ff Merge branch 'jc/spell-id-in-both-caps-in-message-id'
next prev parent reply other threads:[~2023-09-20 15:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 12:56 [REGRESSION] uninitialized value $address in git send-email Bagas Sanjaya
2023-09-18 16:35 ` [PATCH] git-send-email.perl: avoid printing undef when validating addresses Taylor Blau
2023-09-18 19:04 ` Junio C Hamano
2023-09-18 21:20 ` Jeff King
2023-09-18 20:26 ` [REGRESSION] uninitialized value $address in git send-email Michael Strawbridge
2023-09-19 4:44 ` Bagas Sanjaya
2023-09-19 14:04 ` Michael Strawbridge
2023-09-19 14:37 ` Michael Strawbridge
2023-09-20 11:00 ` Bagas Sanjaya
2023-09-20 13:14 ` Michael Strawbridge
2023-09-20 15:43 ` Junio C Hamano [this message]
2023-09-21 7:51 ` Bagas Sanjaya
2023-09-21 20:42 ` Junio C Hamano
2023-09-22 7:39 ` Bagas Sanjaya
2023-09-20 15:36 ` Junio C Hamano
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=xmqq7cokc0kj.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=dianders@chromium.org \
--cc=git@vger.kernel.org \
--cc=luben.tuikov@amd.com \
--cc=michael.strawbridge@amd.com \
--cc=nasamuffin@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.