From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 105350 invoked by alias); 20 Sep 2017 15:05:54 -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 105299 invoked by uid 89); 20 Sep 2017 15:05:54 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=joel, Automatic, verifiable, Joel X-Spam-User: qpsmtpd, 2 recipients X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 20 Sep 2017 15:05:52 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id A3BD756452; Wed, 20 Sep 2017 11:05:50 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Q01OQvZM-IlR; Wed, 20 Sep 2017 11:05:50 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 713A756451; Wed, 20 Sep 2017 11:05:50 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id B06648305C; Wed, 20 Sep 2017 08:05:48 -0700 (PDT) Date: Wed, 20 Sep 2017 15:05:00 -0000 From: Joel Brobecker To: Petr Ovtchenkov Cc: binutils@sourceware.org, gdb@sourceware.org Subject: Re: meaning of "Automatic date update in version.in" commits Message-ID: <20170920150548.rj235a6sjxsnusrj@adacore.com> References: <20170920173622.28500ccf@void-ptr.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170920173622.28500ccf@void-ptr.info> User-Agent: NeoMutt/20170113 (1.7.2) X-SW-Source: 2017-09/txt/msg00051.txt.bz2 [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 > 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... -- Joel