From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 70578 invoked by alias); 21 Sep 2017 17:07:34 -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 69413 invoked by uid 89); 21 Sep 2017 17:07:34 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,RP_MATCHES_RCVD,SPF_PASS,URIBL_SBL autolearn=no version=3.3.2 spammy=CVS, cvs, historically, daily X-HELO: mail-yw0-f169.google.com Received: from mail-yw0-f169.google.com (HELO mail-yw0-f169.google.com) (209.85.161.169) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 21 Sep 2017 17:07:32 +0000 Received: by mail-yw0-f169.google.com with SMTP id t127so4508290ywg.4 for ; Thu, 21 Sep 2017 10:07:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5KX/H8a+IZsDjabNBRbyNJfEnEjtR4yso3TWK+Ay+qQ=; b=nuswEYPRTqn8TIc8A2lUHoPJGYmCph3bDGUa/yX4IcPRTf37hwmEGQpGL13gbdi4oD WwqIN8C969H2HGTBY3CaVgbY4ZbWpPxA//YtjLi+7t50F29h2pXm77Yx+6+4cMIU++n3 lAY3fFUa3528c1o5GESUtgzAk80s/OVVwlXzJhWLlwqmoSXjlWCOTj4k8G1gfBwhja5M TZFFWN+Q3kCPCPRsweMZAvUeAfeAAgEGBp6zvJeUI7lbjcwIfGno62hECfG4QBcaEw3W Sq7r/fx0agZVBIjBnEtzwYrMjgpn86q/xFgCDF1uIc6NMm5NOqi6xUWzq9fGo7ZtqHrv 5sYg== X-Gm-Message-State: AHPjjUgs0+15pPx88bi+6NXe527IdOJcYN8PTo3JX/DFXnTsLF8jjSpX 1uzVe9lAlDD/R0+JmMTGeKE8BSQm/jiqGh82AR1ucFiL X-Google-Smtp-Source: AOwi7QAtm7dhgA699FinM1mrvxXzk8yxDO6B1Wnr64m1xoGgMQIlw/RAfdDO6+QctPgsdOAebVvUTUysoL1oAwOcwMI= X-Received: by 10.37.214.150 with SMTP id n144mr2028262ybg.50.1506013650754; Thu, 21 Sep 2017 10:07:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.129.108.79 with HTTP; Thu, 21 Sep 2017 10:07:30 -0700 (PDT) In-Reply-To: <20170920183312.73ade4ef@void-ptr.info> References: <20170920173622.28500ccf@void-ptr.info> <20170920150548.rj235a6sjxsnusrj@adacore.com> <20170920183312.73ade4ef@void-ptr.info> From: "Ian Lance Taylor via gdb" Reply-To: Ian Lance Taylor Date: Thu, 21 Sep 2017 17:07:00 -0000 Message-ID: Subject: Re: meaning of "Automatic date update in version.in" commits To: Petr Ovtchenkov Cc: Joel Brobecker , Binutils , gdb Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2017-09/txt/msg00088.txt.bz2 On Wed, Sep 20, 2017 at 8:33 AM, Petr Ovtchenkov wrote: > On Wed, 20 Sep 2017 08:05:48 -0700 > 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 >> > 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... >> > > For [possible] transition/solution/etc it would be useful to tell here what > this ["Automatic date update in version.in"] commits was intended for. Historically speaking, my recollection is that Ken Raeburn introduced it around 1994 or so when he started producing daily binutils snapshots. At the time the binutils source code repository was not publicly available: it was held internally on the Cygnus CVS server (the binutils source code repo was not publicly accessible until 1999). Ken started making daily snapshots of the code available via FTP for non-Cygnus developers and users. The daily snapshots were named after the day, naturally, and he added code to record the day in the version file so that people knew which snapshot had been used to build the tools. As people have said it is now also used as part of the libbfd SONAME, but at the time that Ken introduced it there was no support for building BFD as a shared library. Ian