git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Michael Strawbridge" <michael.strawbridge@amd.com>,
	"Luben Tuikov" <luben.tuikov@amd.com>,
	git@vger.kernel.org, entwicklung@pengutronix.de
Subject: Re: Regression: git send-email fails with "Use of uninitialized value $address" + "unable to extract a valid address"
Date: Thu, 26 Oct 2023 21:41:27 +0900	[thread overview]
Message-ID: <xmqqsf5xr1xk.fsf@gitster.g> (raw)
In-Reply-To: <20231025072104.GA2145145@coredump.intra.peff.net> (Jeff King's message of "Wed, 25 Oct 2023 03:21:04 -0400")

Jeff King <peff@peff.net> writes:

> Note that the bug will only trigger if Email::Valid is installed.

I recall we chased a different bug that depends on the use/non-use
of this package a few years ago.  Is the difference significant
enough that we may want to install on one but not in another CI
environment, like we have a separate CI jobs with exotic settings, I
wonder.

  parent reply	other threads:[~2023-10-26 12:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 14:14 Regression: git send-email fails with "Use of uninitialized value $address" + "unable to extract a valid address" Uwe Kleine-König
2023-10-13 15:07 ` Kristoffer Haugsbakk
2023-10-20 10:04 ` Uwe Kleine-König
2023-10-20 21:06   ` Michael Strawbridge
2023-10-24 13:00     ` Uwe Kleine-König
2023-10-24 19:00       ` Michael Strawbridge
2023-10-24 20:43         ` Uwe Kleine-König
2023-10-25  7:21           ` Jeff King
2023-10-25  7:40             ` Uwe Kleine-König
2023-10-26 12:41             ` Junio C Hamano [this message]
2023-10-26 13:07               ` Michael Strawbridge
2023-10-26 14:46                 ` Todd Zullinger
2023-10-27 15:44                   ` Junio C Hamano
2023-10-30  9:29                   ` Jeff King

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=xmqqsf5xr1xk.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=entwicklung@pengutronix.de \
    --cc=git@vger.kernel.org \
    --cc=luben.tuikov@amd.com \
    --cc=michael.strawbridge@amd.com \
    --cc=peff@peff.net \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).