From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5019 invoked by alias); 20 Sep 2017 15:48:25 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 4999 invoked by uid 89); 20 Sep 2017 15:48:24 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=Hx-languages-length:1674, 2, daily, H*c:application X-Spam-User: qpsmtpd, 2 recipients X-HELO: mircat.net Received: from mircat.net (HELO mircat.net) (81.9.105.50) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 20 Sep 2017 15:48:23 +0000 Received: from [84.47.189.162] (port=41960 helo=[172.27.105.69]) by mircat.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from ) id 1duhEX-000Ku4-JY; Wed, 20 Sep 2017 18:48:17 +0300 Subject: Re: meaning of "Automatic date update in version.in" commits To: Matthias Klose , Joel Brobecker , Petr Ovtchenkov Cc: binutils@sourceware.org, gdb@sourceware.org References: <20170920173622.28500ccf@void-ptr.info> <20170920150548.rj235a6sjxsnusrj@adacore.com> From: Dmitry Samersoff Message-ID: <632663a3-d907-25f8-5ea5-e9db91ec7643@samersoff.net> Date: Wed, 20 Sep 2017 15:48:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="UATFNv4hmmeuBXApWBSXS7sq36I9cdIpI" X-Authenticated-As: dms X-SpamProbe: GOOD 0.0000028 a7410e189059de5367d31f8e6b06fcb0 X-IsSubscribed: yes X-SW-Source: 2017-09/txt/msg00054.txt.bz2 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --UATFNv4hmmeuBXApWBSXS7sq36I9cdIpI Content-Type: multipart/mixed; boundary="42xwkFJBBlhpTgAMKIPrvfKhPGrfDDfbR"; protected-headers="v1" From: Dmitry Samersoff To: Matthias Klose , Joel Brobecker , Petr Ovtchenkov Cc: binutils@sourceware.org, gdb@sourceware.org Message-ID: <632663a3-d907-25f8-5ea5-e9db91ec7643@samersoff.net> Subject: Re: meaning of "Automatic date update in version.in" commits References: <20170920173622.28500ccf@void-ptr.info> <20170920150548.rj235a6sjxsnusrj@adacore.com> In-Reply-To: --42xwkFJBBlhpTgAMKIPrvfKhPGrfDDfbR Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Content-length: 1633 On 20.09.2017 18:39, Matthias Klose wrote: > On 20.09.2017 17:05, Joel Brobecker wrote: >> [adding the GDB group, as this affects both] >> >>> What is the meaning of "Automatic date update in version.in" commits? >>> I mean commits like f625a739e5. >>> >>> This commits litter commits tree and create problems for=20=20=09 >>> deterministic, bit-identical and/or verifiable builds. >>> >>> May be worth to remove this (historical?) artifact? >> >> We've had that discussion several times in the past. I'd be quite >> happy to get rid of that daily commit, and most people here probably >> would be too. The issue is that no one has been able to get us >> to agree on what we should be doing instead, and then implement it. >> Part of the obstacles, I think, is that everyone has their own idea >> of the requirements that should be met. Maybe one solution would be >> to ask the group of Global Maintainers to make a decision (at least >> for GDB) once everyone had a chance to provide their feedback. Once >> we have a clear plan of what should be done, I suspect finding >> a volunteer to implement it wouldn't be too hard. I might even >> take an hour or two in a weekend to look into that... >=20 > For binutils the date gets encoded into the libbfd and libopcodes soname,= so you > are pretty safe during development. Maybe you could manually bump the ve= rsion > when it is needed, but I assume that is more difficult than the automated= daily > bump. If it's the only purpose of daily commit, than the obvious solution is to improve daily commit script and update version.in only if source code changes. My $.2 -Dmitry --42xwkFJBBlhpTgAMKIPrvfKhPGrfDDfbR-- --UATFNv4hmmeuBXApWBSXS7sq36I9cdIpI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" Content-length: 473 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJZwo3BAAoJEHEy08c4gIAB+1QIAJc0sZCehJOhUtcxOmgiMhE1 /1ARH3C+5cFKGlgYhB+m6QXAZ/uT5/mplDvjefbQ93VI+d3nvxpzfJ4m2L/bACjY GdsUfg4jwRJsxAlhp6WPnv8N/Rv9LquliRW1ZRTwVSUVvAxBYJxx7DypqVk3et4m +3jmOI1ZSUGrXm1zanJTqyWGtLiixH6Hx6Bxup2EG9a8+a3HyBMpa3kYUzIqrx68 eGxm7TxmjnS9gOeKl/S0f6ioMGtGcIE8jw03CX3zxvEqpkhwpDiYkEr3tbZPlv/+ 74DFoH24gf27Fbv/ky2p1WqDAMdRzypNoMXgW/iCueRv9cxulJoBhIutTw/cDbw= =Ep8W -----END PGP SIGNATURE----- --UATFNv4hmmeuBXApWBSXS7sq36I9cdIpI--