From: Dani Moncayo <dmoncayo@gmail.com>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
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 13:16:59 +0200 [thread overview]
Message-ID: <CAH8Pv0j2Ph=zbrqU3hZwnOF-yHn1FHMJHUjZNivSLaj=53Wxog@mail.gmail.com> (raw)
In-Reply-To: <87bo2uhie3.fsf@wanadoo.es>
>>> IOW, the revision-id is enough to unequivocally identify the revision
>>> in any given branch.
>>
>> Of course, but that would require the user to have bzr installed, just
>> to get the revnos from the revids. That would be too bad, and can be
>> easily avoided just by including the revnos in the git notes.
>
> Why is the *user* interested on getting the revno? For bug reporting,
> the revid is perfectly valid (and, as stated before, it is more precise
> than the revno.)
(I think I didn't answer to your question in my previous reply. Sorry.)
Many people prefer to use revnos while reporting bugs or discussing
changes (this mailing list is the clearest example).
I was even asked to include that revnos in the binaries I publish, see:
http://lists.gnu.org/archive/html/help-gnu-emacs/2013-10/msg00002.html
So, even though the bzr revision IDs are unambiguous, (most) humans
prefer to use the revision numbers.
--
Dani Moncayo
next prev parent reply other threads:[~2013-10-12 11:16 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH8Pv0j2Ph=zbrqU3hZwnOF-yHn1FHMJHUjZNivSLaj=53Wxog@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).