From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by sourceware.org (Postfix) with ESMTPS id B0E773858C60 for ; Mon, 10 Jan 2022 17:52:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B0E773858C60 Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id 20AHqfFZ015988 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 10 Jan 2022 12:52:45 -0500 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 20AHqfFZ015988 Received: from [10.0.0.11] (192-222-157-6.qc.cable.ebox.net [192.222.157.6]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id E5F5D1E61F; Mon, 10 Jan 2022 12:52:40 -0500 (EST) Message-ID: Date: Mon, 10 Jan 2022 12:52:40 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.4.0 Subject: Re: [PATCH] gdbsupport: regenerate Makefile.in Content-Language: en-US To: Andrew Burgess , gdb-patches@sourceware.org References: <20220110174634.890984-1-aburgess@redhat.com> From: Simon Marchi In-Reply-To: <20220110174634.890984-1-aburgess@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Mon, 10 Jan 2022 17:52:41 +0000 X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2022 17:52:48 -0000 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