From: Simon Marchi <simon.marchi@polymtl.ca>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdbsupport: regenerate Makefile.in
Date: Mon, 10 Jan 2022 12:52:40 -0500 [thread overview]
Message-ID: <d28b4948-a334-553f-fec7-bb995fe84189@polymtl.ca> (raw)
In-Reply-To: <20220110174634.890984-1-aburgess@redhat.com>
On 2022-01-10 12:46, Andrew Burgess via Gdb-patches wrote:
> I had cause to regenerate gdbsupport/Makefile.in, and noticed some
> unexpected changes in the copyright header dates.
>
> I suspect that this was caused by the end of year date range update
> process.
>
> The Makefile.in contains two date ranges. The first range appears to
> be the date range for the version of automake being used, that is the
> range runs up to 2017 only, when automake 1.15.1 was released.
>
> The second date range in Makefile.in represents the date range for the
> generated file, and so, now runs up to 2022.
>
> Anyway, this is the result of running autoreconf (using automake
> 1.15.1) in the gdbsupport directory.
Looks obvious to me, indeed the copyright update tool seems to get this
wrong. Either the tool should have a special case (which seems difficult),
or the end-of-year procedure could include "re-generate the Makefiles" at
the end, that would automatically revert these wrong automated changes.
Simon
next prev parent reply other threads:[~2022-01-10 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 17:46 Andrew Burgess
2022-01-10 17:52 ` Simon Marchi [this message]
2022-01-16 9:53 ` Joel Brobecker
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=d28b4948-a334-553f-fec7-bb995fe84189@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.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).