From: Todd Zullinger <tmz@pobox.com>
To: "H.Merijn Brand" <linux@tux.freedom.nl>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Fix git-send-email.perl w.r.t. recent Getopt::Long update
Date: Mon, 27 Nov 2023 21:07:00 -0500 [thread overview]
Message-ID: <ZWVLRIfARhRhz-7L@pobox.com> (raw)
In-Reply-To: <20231127093810.2092fe1d@pc09>
Hi,
H.Merijn Brand wrote:
> On Mon, 27 Nov 2023 09:58:52 +0900, Junio C Hamano <gitster@pobox.com> wrote:
>> One downside of unconditional upgrade of the call is, of course,
>> that it would no longer work for those with older Getopt::Long that
>> did not support the "!" suffix. Fortunately, Getopt::Long 2.33
>> started shipping with Perl 5.8.1 that is more than 20 years old, so
>> with the series we accepted, we also have a change to bump the
>> required version of Perl from 5.8.0 to 5.8.1 to make it clear that
>> it is deliberate that we drop the support for anything older at the
>> same time.
>
> The is a no-issue ...
>
> Just the 'use Getopt::Long' is enough to guarantee a working version:
>
> The '!' was already implemented in version 2.10 (April 1997):
> --8<---
> =item !
>
> Option does not take an argument and may be negated, i.e. prefixed by
> "no". E.g. "foo!" will allow B<--foo> (with value 1) and B<-nofoo>
> (with value 0).
> The option variable will be set to 1, or 0 if negated.
> -->8---
The real issue is the lack of support for the '--no-' prefix
when used with the '!' parameter. The '--no-' form is what
has always been documented by git-send-email(1). It was not
supported until Getopt::Long 2.33, included in perl 5.8.1.
Prior, 'foo!' provided --foo and --nofoo but not --no-foo.
But as Junio said, we can accept requiring a perl which was
released sometime in the past 2 decades in order to run the
most recent git release. ;)
Thanks for noticing this and sending a patch!
--
Todd
prev parent reply other threads:[~2023-11-28 2:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 9:39 Fix git-send-email.perl w.r.t. recent Getopt::Long update H.Merijn Brand
2023-11-25 2:22 ` Bagas Sanjaya
2023-11-25 9:45 ` H.Merijn Brand
2023-11-25 12:28 ` Dragan Simic
2023-11-27 21:38 ` Jeff King
2023-11-27 0:58 ` Junio C Hamano
2023-11-27 8:38 ` H.Merijn Brand
2023-11-28 2:07 ` Todd Zullinger [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=ZWVLRIfARhRhz-7L@pobox.com \
--to=tmz@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux@tux.freedom.nl \
/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).