[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: empty TIMESTAMP, stamp-vcl
From: |
Eric Blake |
Subject: |
Re: empty TIMESTAMP, stamp-vcl |
Date: |
Wed, 28 Mar 2007 13:12:00 -0600 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.10) Gecko/20070221 Thunderbird/1.5.0.10 Mnenhy/0.7.4.666 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Gary V. Vaughan on 3/28/2007 10:07 AM:
> Consider that the timestamp is there to allow us to pull the exact version
> a bug-reporter used by reference to the version string we hope they quote.
> It doesn't actually matter what we use for that string, just that we can
> get back to the same build that generated the bug-report.
>
> There are two implications:
> i) if we master from git, then the git revision hash gives us that,
> as long as we push that information into the CVS mirror.
> ii) except that doesn't tell us which gnulib release was used, so we
> need to factor the gnulib timestamp information too :-( I think
> we can maybe get away with just making bootstrap write a gnulib
> repo timestamp into a version.c file...
>
> On the other hand maybe we can persuade the gnulib folks to have a proper
> release schedule, or else add something to gnulib-tool to help us keep
> track of the particular non-releases the bug-reporter bootstrapped with?
Now that you mention it, it would be nice if every invocation of
'gnulib-tool --update' or 'gnulib-tool --import' would touch a timestamp
file that could then be incorporated into the project.
- --
Don't work too hard, make some time for fun as well!
Eric Blake address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGCr3/84KuGfSFAYARAknqAJ9Rg7subJSTOIHuaknRqtwFykMBOgCg0ceC
MDuo1XjdAFGjLizN5vrfOfc=
=S6N2
-----END PGP SIGNATURE-----