Mark H Weaver skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Eric Bavier skribis:
>>
>>> I realize we have no guidelines in the manual concerning the version
>>> field for git checkouts, but I wonder whether we should, as it comes up
>>> a bit. Several existing packages use (string-appe
On Wed, Sep 23, 2015 at 07:35:41PM -0400, Mark H Weaver wrote:
> I'd like to propose another alternative, which I used for 'grub' on the
> 'wip-loongson2f' branch. There, the version string is simply the output
> of "git describe". This gives us lexicographic ordering, and the commit
> id can be
l...@gnu.org (Ludovic Courtès) writes:
> Eric Bavier skribis:
>
>> I realize we have no guidelines in the manual concerning the version
>> field for git checkouts, but I wonder whether we should, as it comes up
>> a bit. Several existing packages use (string-append "1.2.3." commit),
>> where "1.
Ludovic Courtès writes:
> Instead we should use (string-append "1.2.3." REV "." commit) where REV
> would be an integer we manually increment every time we upgrade to a
> newer snapshot.
>
> I don’t think adding “-” or “-c” before the commit is useful, but I
> don’t have a strong opinion.
Good i
Eric Bavier skribis:
> I realize we have no guidelines in the manual concerning the version
> field for git checkouts, but I wonder whether we should, as it comes up
> a bit. Several existing packages use (string-append "1.2.3." commit),
> where "1.2.3" is the version of the corresponding source
