[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Setting the value of `emacs-bzr-version' also from a git checkout

From: Óscar Fuentes
Subject: Re: Setting the value of `emacs-bzr-version' also from a git checkout
Date: Sat, 12 Oct 2013 23:38:51 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Dani Moncayo <address@hidden> writes:

> Yes, but note that the bzr revision numbers have an advantage over the
> revision IDs: they are numeric, so you can easily tell whether a given
> revno is newer or older that another one.
> So, for example if you know that one bug was fixed in revno 100200,
> and you see one user reporting a similar bug with revno 100150, you
> _immediately_ know that this user is running an older version which
> does not include the bug fix.

Yes, and IIRC that's why there is some prominent people on the git
community that miss sequential revision numbers.

> But I also understand what you say: The revnos are ambiguous when you
> don't specify the branch they come from.

Exactly. Revision numbers are okay when you know the branch, but a
potential source of confusion on any other case.

> In any case, what I'm trying to do here is simply making
> "emacs-bzr-version" give the same info (i.e. both the revno and the
> revid) from a binary made from either bzr-trunk or its official git
> counterpart (savannah's git mirror).

And the message that I'm trying to send is that you already did the
really useful part. I also build Emacs from git and I think it is a good
thing to put the bzr revid on them. The difficulties you are facing now
is with a bit of information that is not really required, once you have
the revid, so I'll say don't bother with it and thank you for your work

reply via email to

[Prev in Thread] Current Thread [Next in Thread]