From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: perl-5.36.1-1 and Perl distributions
Date: Sun, 7 May 2023 21:50:29 -0600 [thread overview]
Message-ID: <a4cadb28-2ca2-b040-437a-13f53056553e@Shaw.ca> (raw)
In-Reply-To: <announce.87a5ym4jby.fsf@Rainer.invalid>
On 2023-05-02 13:36, Achim Gratz via Cygwin wrote:
> Perl 5.36.1-1 is now available on Cygwin, replacing perl-5.32.1. Most
> Perl distributions and dependent packages have been either re-released
> or updated in conjunction with this update. The following packages have
> been released for Cygwin:
Hi folks,
Just updated everything including perl and now git send-email fails with error
without prompting or requesting input for sendemail.confirm = always - address
headers have been sanitized and perl indents have been reduced:
$ git send-email --to=patches
0001-fhandler-proc.cc-format_proc_cpuinfo-Add-Linux-6.3-cpuinfo.patch
0001-fhandler-proc.cc-format_proc_cpuinfo-Add-Linux-6.3-cpuinfo.patch
(mbox) Adding to: patches from line 'To: patches'
From: user.name <user.email>
To: patches
Subject: [PATCH] fhandler/proc.cc(format_proc_cpuinfo): Add Linux 6.3 cpuinfo
Date: Sun, 7 May 2023 16:07:20 -0600
Message-Id: <68bbf3607bdf37fcd32613aa962abe50846d968a.1682994011.git.user.email>
X-Mailer: git-send-email 2.39.0
MIME-Version: 1.0
Bcc: user.name <user.email>
Reply-To: patches
Content-Transfer-Encoding: 8bit
Send this email reply required at /usr/libexec/git-core/git-send-email line 1585.
$
git-send-email:
1561 if ($needs_confirm && !$dry_run) {
1562 print "\n$header\n";
1563 if ($needs_confirm eq "inform") {
1564 $confirm_unconfigured = 0; # squelch this message for the rest of this run
1565 $ask_default = "y"; # assume yes on EOF since user hasn't explicitly asked
for confirmation
1566 print __ <<EOF ;
1567 The Cc list above has been expanded by additional
1568 addresses found in the patch commit message. By default
1569 send-email prompts before sending whenever this occurs.
1570 This behavior is controlled by the sendemail.confirm
1571 configuration setting.
1572
1573 For additional information, run 'git send-email --help'.
1574 To retain the current behavior, but squelch this message,
1575 run 'git config --global sendemail.confirm auto'.
1576
1577 EOF
1578 }
1579 # TRANSLATORS: Make sure to include [y] [n] [e] [q] [a] in your
1580 # translation. The program will only accept English input
1581 # at this point.
1582 $_ = ask(__("Send this email? ([y]es|[n]o|[e]dit|[q]uit|[a]ll): "),
1583 valid_re => qr/^(?:yes|y|no|n|edit|e|quit|q|all|a)/i,
1584 default => $ask_default);
1585 die __("Send this email reply required") unless defined $_;
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-05-08 3:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 19:36 Achim Gratz
2023-05-08 3:50 ` Brian Inglis [this message]
2023-05-09 16:57 ` git-send-email --confirm=always error after perl upgrade Brian Inglis
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=a4cadb28-2ca2-b040-437a-13f53056553e@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin@cygwin.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 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).