Re: meaning of "Automatic date update in version.in" commits

[Petr Ovtchenkov <ptr at void-ptr dot info>]

On Wed, 20 Sep 2017 22:26:44 +0200
Philippe Waroquiers <philippe.waroquiers@skynet.be> wrote:

> On Wed, 2017-09-20 at 22:17 +0200, Matthias Klose wrote:
> > 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.
> 
> I suppose that a development snapshot tarball will always be done
> from a git repository, and so will have the sha1 and date in the
> version.
> 
> And if really someone makes a snapshot outside of a git repository,
> then the resulting snapshot will not be very precisely identified.
> Don't use it :).
> 
> Philippe
> 

Why you forget about
<snip>
  From info above follow, that "Automatic date update in version.in" give nothing
  useful.

  From datestamps equality not follow ABI compatibility from one side,
  and from datestamps inequality not follow ABI incompatibility from another side.
</snip>
?

--

  - ptr