From: Dani Moncayo <dmoncayo@gmail.com>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Setting the value of `emacs-bzr-version' also from a git checkout
Date: Sat, 12 Oct 2013 23:25:25 +0200 [thread overview]
Message-ID: <CAH8Pv0iC5jFtC4Ck2_eMHvYMsMcNc-pok5kUc5r+HQk7TqqHhg@mail.gmail.com> (raw)
In-Reply-To: <871u3qgvk2.fsf@wanadoo.es>
> That's because they don't understand the implications. The usefulness of
> including version info on bug reports (something that IIRC is done
> automatically, so there is no need to show the info on screenshots, etc)
> is to pinpoint the sources used for the build.
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.
But I also understand what you say: The revnos are ambiguous when you
don't specify the branch they come from.
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).
--
Dani Moncayo
next prev parent reply other threads:[~2013-10-12 21:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 16:45 Setting the value of `emacs-bzr-version' also from a git checkout (was: Emacs trunk binary on Dropbox) Dani Moncayo
2013-10-01 17:04 ` Setting the value of `emacs-bzr-version' also from a git checkout Óscar Fuentes
2013-10-01 17:45 ` Andreas Schwab
2013-10-01 18:37 ` Dani Moncayo
2013-10-01 18:46 ` Óscar Fuentes
2013-10-01 21:15 ` Dani Moncayo
2013-10-02 0:22 ` Stefan Monnier
2013-10-02 14:36 ` Josh
2013-10-12 10:22 ` Dani Moncayo
2013-10-12 10:33 ` Eli Zaretskii
2013-10-12 10:42 ` Dani Moncayo
2013-10-12 10:51 ` Óscar Fuentes
2013-10-12 10:58 ` Dani Moncayo
2013-10-12 11:16 ` Dani Moncayo
2013-10-12 11:40 ` Eli Zaretskii
2013-10-12 12:04 ` Dani Moncayo
2013-10-12 19:04 ` Óscar Fuentes
2013-10-12 20:36 ` Juanma Barranquero
2013-10-12 20:51 ` Óscar Fuentes
2013-10-12 20:57 ` Juanma Barranquero
2013-10-12 21:16 ` Óscar Fuentes
2013-10-12 21:33 ` Juanma Barranquero
2013-10-12 20:56 ` Stefan Monnier
2013-10-12 21:25 ` Dani Moncayo [this message]
2013-10-12 21:38 ` Óscar Fuentes
2013-10-12 10:58 ` Eli Zaretskii
2013-10-12 11:06 ` Dani Moncayo
2013-10-12 11:37 ` Eli Zaretskii
2013-10-13 20:49 ` Dani Moncayo
2013-10-13 22:16 ` Glenn Morris
2013-10-14 6:38 ` Dani Moncayo
-- strict thread matches above, loose matches on Subject: below --
2013-10-01 20:23 Dani Moncayo
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=CAH8Pv0iC5jFtC4Ck2_eMHvYMsMcNc-pok5kUc5r+HQk7TqqHhg@mail.gmail.com \
--to=dmoncayo@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.