From: Bernhard Voelker <mail@bernhard-voelker.de>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Cc: "Brian C. Lane" <bcl@redhat.com>
Subject: Re: update-copyright is broken
Date: Wed, 17 Jul 2019 08:44:28 +0200 [thread overview]
Message-ID: <1e10d06b-d1db-448b-1916-2c7d6973008a@bernhard-voelker.de> (raw)
In-Reply-To: <2702799.gSeAclHnIc@omega>
On 7/16/19 10:03 AM, Bruno Haible wrote:
> Thanks for the report. Indeed, a bad regression. Fixed as follows:
Hmm, and what about the other changes of perl options in commit a05d5d121b10:
* build-aux/useless-if-before-free:
had tainting checks enabled (-T):
< eval 'exec perl -wST "$0" "$@"'
> eval 'exec perl -wSx "$0" "$@"'
* tests/test-update-copyright.sh:
had -0777 -pi:
< eval 'exec perl -wS -0777 -pi "$0" "$@"'
> eval 'exec perl -wSx "$0" "$@"'
?
Are they consciously dropped?
announce-gen, gitlog-to-changelog and prefix-gnulib-mk still have
their original perl options BTW.
Have a nice day,
Berny
next prev parent reply other threads:[~2019-07-17 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 23:50 update-copyright is broken Brian C. Lane
2019-07-16 8:03 ` Bruno Haible
2019-07-17 6:44 ` Bernhard Voelker [this message]
2019-07-19 23:22 ` Bruno Haible
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: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1e10d06b-d1db-448b-1916-2c7d6973008a@bernhard-voelker.de \
--to=mail@bernhard-voelker.de \
--cc=bcl@redhat.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
/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).