From: Matthias Klose <doko@ubuntu.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
Mikhail Terekhov <Mikhail.Terekhov@dell.com>,
Petr Ovtchenkov <ptr@void-ptr.info>,
Andreas Schwab <schwab@linux-m68k.org>
Cc: binutils@sourceware.org, Joel Brobecker <brobecker@adacore.com>,
gdb@sourceware.org
Subject: Re: meaning of "Automatic date update in version.in" commits
Date: Wed, 20 Sep 2017 20:21:00 -0000 [thread overview]
Message-ID: <74520278-52b3-582f-84c2-d2b4ad2b6ef4@ubuntu.com> (raw)
In-Reply-To: <1505938054.4443.8.camel@skynet.be>
On 20.09.2017 22:07, Philippe Waroquiers wrote:
> On Wed, 2017-09-20 at 21:54 +0200, Matthias Klose wrote:
>
>>>
>>> ~/tmp/gdb/binutils-gdb (master)>git log -1 --format=%cd --
>>> date=format:%Y%m%d
>>> 20170920
>>>
>>> Then there is no need for additional commit.
>>
>> no, you can't assume that git is available for builds.
> In valgrind, the version.h file is build as part of the dist tarball.
> And if really someone just takes a copy of the sources before
> building and/or making the dist tarball, valgrind --version -v
> will just tell that the git version and date is unknown.
but we are talking here about sonames for development snapshots. A soname like
2.29.50.unknown doesn't change.
next prev parent reply other threads:[~2017-09-20 20:21 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
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 [this message]
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=74520278-52b3-582f-84c2-d2b4ad2b6ef4@ubuntu.com \
--to=doko@ubuntu.com \
--cc=Mikhail.Terekhov@dell.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
--cc=ptr@void-ptr.info \
--cc=schwab@linux-m68k.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