From: Jim Meyering <email@example.com>
Subject: Re: FYI: update-copyright: also work with two or more updatable lines
Date: Tue, 10 Jan 2023 21:19:49 -0800 [thread overview]
Message-ID: <CA+8g5KHh18oArrKtpcBxBvqFJ_x214h97HbaJMpA51RqLOUJfirstname.lastname@example.org> (raw)
On Tue, Jan 10, 2023 at 8:37 PM Jim Meyering <email@example.com> wrote:
> FYI, I've just pushed this fix.
> I noticed this bug when attempting to update gzip's copyright dates.
> It has a few files with two copyright lines.
> The old version of this script would update only the first one.
For the record, that fix adds coverage for lines with identical year lists.
This script still does not work for gzip's case in which the year
lists are different.
prev parent reply other threads:[~2023-01-11 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 4:37 FYI: update-copyright: also work with two or more updatable lines Jim Meyering
2023-01-11 5:19 ` Jim Meyering [this message]
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:
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 \
* 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).