public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail•com>
To: Junio C Hamano <gitster@pobox•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: Fri, 22 Sep 2023 14:39:29 +0700	[thread overview]
Message-ID: <ZQ1EsX5ZwkAHgT4Z@debian.me> (raw)
In-Reply-To: <xmqq1qer5kc0.fsf@gitster.g>

[-- Attachment #1: Type: text/plain, Size: 361 bytes --]

On Thu, Sep 21, 2023 at 01:42:55PM -0700, Junio C Hamano wrote:
> Bagas Sanjaya <bagasdotme@gmail•com> writes:
> > I'll make one on the separate report.
> 
> Alright.  The next task from your end may be to see if you can
> bisect to find which topic broke your expectation.
> 

OK, thanks!

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-09-22  7:39 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
2023-09-21  7:51             ` Bagas Sanjaya
2023-09-21 20:42               ` Junio C Hamano
2023-09-22  7:39                 ` Bagas Sanjaya [this message]
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=ZQ1EsX5ZwkAHgT4Z@debian.me \
    --to=bagasdotme@gmail$(echo .)com \
    --cc=avarab@gmail$(echo .)com \
    --cc=dianders@chromium$(echo .)org \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    --cc=luben.tuikov@amd$(echo .)com \
    --cc=michael.strawbridge@amd$(echo .)com \
    --cc=nasamuffin@google$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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