From: Junio C Hamano <gitster@pobox.com>
To: Todd Zullinger <tmz@pobox.com>
Cc: "Jeff King" <peff@peff.net>,
git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Ondřej Pohořelský" <opohorel@redhat.com>
Subject: Re: [PATCH] send-email: avoid duplicate specification warnings
Date: Wed, 15 Nov 2023 09:48:45 +0900 [thread overview]
Message-ID: <xmqqy1ezx2mq.fsf@gitster.g> (raw)
In-Reply-To: <ZVPfvjoXyGVlKqvr@pobox.com> (Todd Zullinger's message of "Tue, 14 Nov 2023 15:59:42 -0500")
Todd Zullinger <tmz@pobox.com> writes:
> Since this isn't anything new with 2.43, it doesn't need to
> be fixed with much urgency.
True. Unless the new version of Getopt::Long is quickly spreading
through our user base, that is.
> Thanks both,
Thanks for spotting the issue and acting on it quickly.
next prev parent reply other threads:[~2023-11-15 0:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 16:38 [PATCH] send-email: avoid duplicate specification warnings Todd Zullinger
2023-11-14 17:32 ` Junio C Hamano
2023-11-14 20:00 ` Jeff King
2023-11-14 20:59 ` Todd Zullinger
2023-11-15 0:48 ` Junio C Hamano [this message]
2023-11-15 17:39 ` [RFC PATCH v2 0/2] " Todd Zullinger
2023-11-15 17:39 ` [RFC PATCH v2 1/2] " Todd Zullinger
2023-11-16 4:58 ` Junio C Hamano
2023-11-16 19:30 ` [PATCH v3 0/2] " Todd Zullinger
2023-11-16 19:30 ` [PATCH v3 1/2] perl: bump the required Perl version to 5.8.1 from 5.8.0 Todd Zullinger
2023-11-16 20:16 ` Jeff King
2023-11-16 19:30 ` [PATCH v3 2/2] send-email: avoid duplicate specification warnings Todd Zullinger
2023-11-16 22:32 ` [PATCH v3 0/2] " Junio C Hamano
2023-11-15 17:39 ` [RFC PATCH v2 2/2] send-email: remove stray characters from usage Todd Zullinger
2023-11-16 4:59 ` Junio C Hamano
2023-11-16 19:36 ` [PATCH] " Todd Zullinger
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqy1ezx2mq.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=opohorel@redhat.com \
--cc=peff@peff.net \
--cc=tmz@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).