Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Petr Ovtchenkov <ptr@void-ptr.info>
To: Joel Brobecker <brobecker@adacore.com>
Cc: binutils@sourceware.org, gdb@sourceware.org
Subject: Re: meaning of "Automatic date update in version.in" commits
Date: Wed, 20 Sep 2017 15:33:00 -0000	[thread overview]
Message-ID: <20170920183312.73ade4ef@void-ptr.info> (raw)
In-Reply-To: <20170920150548.rj235a6sjxsnusrj@adacore.com>

On Wed, 20 Sep 2017 08:05:48 -0700
Joel Brobecker <brobecker@adacore.com> 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.

Thanks,

--

   - ptr


  reply	other threads:[~2017-09-20 15:33 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170920173622.28500ccf@void-ptr.info>
2017-09-20 15:05 ` Joel Brobecker
2017-09-20 15:33   ` Petr Ovtchenkov [this message]
2017-09-21 17:07     ` Ian Lance Taylor via gdb
2017-09-20 15:40   ` Matthias Klose
2017-09-20 15:48     ` Dmitry Samersoff
     [not found] ` <87zi9p2vma.fsf@linux-m68k.org>
2017-09-20 17:24   ` Petr Ovtchenkov
     [not found]     ` <7217d33d-61eb-732e-dfd6-80ef4908743e@ubuntu.com>
2017-09-20 19:21       ` Petr Ovtchenkov
2017-09-20 19:27       ` Mikhail Terekhov
2017-09-20 19:56         ` Philippe Waroquiers
2017-09-20 19:57         ` Matthias Klose
2017-09-20 20:07           ` Philippe Waroquiers
2017-09-20 20:21             ` Matthias Klose
2017-09-20 20:26               ` Philippe Waroquiers
2017-09-20 20:31                 ` Petr Ovtchenkov
2017-09-20 20:39                   ` Philippe Waroquiers
2017-09-20 20:34           ` Mikhail Terekhov
2017-09-20 21:34     ` Andreas Schwab
2017-09-21  5:03 Fiodar Stryzhniou via gdb
2017-09-21  8:42 ` Matt Rice
2017-09-21 10:58   ` Petr Ovtchenkov
2017-09-21 11:37     ` Pedro Alves
     [not found]       ` <20170921152240.16bb4cc0@void-ptr.info>
2017-09-21 12:39         ` Pedro Alves
2017-09-21 13:17           ` Petr Ovtchenkov
2017-09-21 13:34             ` Simon Marchi
2017-09-21 15:46               ` Petr Ovtchenkov
2017-09-21 16:01                 ` Simon Marchi
2017-09-21 16:03                 ` Matthias Klose
2017-09-21 16:26                   ` Petr Ovtchenkov
2017-09-21 16:34                     ` Joel Brobecker
2017-09-21 16:52                       ` Petr Ovtchenkov
2017-09-21 17:00                         ` Joel Brobecker
2017-09-21 17:39                           ` Petr Ovtchenkov
2017-09-21 23:59                             ` Alan Modra
2017-09-22  5:31                               ` Petr Ovtchenkov
2017-09-22  6:49                                 ` Andreas Schwab
2017-09-22  9:29                                   ` Petr Ovtchenkov
2017-09-22 22:26                                   ` H.J. Lu
2017-09-22 22:35                                   ` H.J. Lu
2017-09-21 17:17   ` Joseph Myers
2017-09-21 17:31     ` Matt Rice

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=20170920183312.73ade4ef@void-ptr.info \
    --to=ptr@void-ptr.info \
    --cc=binutils@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=gdb@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