From: Giorgos Keramidas <keramida@ceid.upatras.gr>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: Emacs <emacs-devel@gnu.org>, Angelo Graziosi <angelo.graziosi@alice.it>
Subject: Re: A little suggestion
Date: Tue, 05 Jan 2010 23:26:36 +0200 [thread overview]
Message-ID: <87d41okzub.fsf@kobe.laptop> (raw)
In-Reply-To: <e01d8a51001050240q7c1c7b69m833930f0f4989677@mail.gmail.com> (Lennart Borgman's message of "Tue, 5 Jan 2010 11:40:36 +0100")
On Tue, 5 Jan 2010 11:40:36 +0100, Lennart Borgman <lennart.borgman@gmail.com> wrote:
> On Tue, Jan 5, 2010 at 11:35 AM, Angelo Graziosi
> <angelo.graziosi@alice.it> wrote:
>> In Emacs, Help | About Emacs, there is written:
>>
>> "GNU Emacs 23.1.91.1 (i686-pc-cygwin, GTK+ Version 2.18.3)
>> of 2010-01-05 on..."
>>
>> Why, in the development stage, not adding the revision number? i.e.:
>>
>> "GNU Emacs 23.1.91.1 rev. 99259..."
>>
>> In GCC, for example, this happens.
>
> I wonder if it is possible? Is it well defined?
>
> Perhaps the beginning and ending time of the checkout could be used
> instead? But I wonder if they are available either.
A revision number like 2100 is *not* well-defined in a DVCS. But there
is a revision identifier that includes a hash we could probably use:
% keramida@kobe:/bzr/emacs/gker$ bzr log --limit 1 --show-ids .
% ------------------------------------------------------------
% revno: 99248
% revision-id: eliz@gnu.org-20100102213336-hnnaav0wq0al1gni
% ...
The `revision-id' value is arguably something that may be useful to have
in `M-x emacs-version' output. At least for non-release builds of Emacs.
next prev parent reply other threads:[~2010-01-05 21:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 10:35 A little suggestion Angelo Graziosi
2010-01-05 10:40 ` Lennart Borgman
2010-01-05 11:05 ` Angelo Graziosi
2010-01-05 11:15 ` Sven Joachim
2010-01-05 21:26 ` Giorgos Keramidas [this message]
2010-01-05 11:23 ` Stephen J. Turnbull
2010-01-05 19:24 ` Eli Zaretskii
2010-01-05 19:55 ` Lennart Borgman
2010-01-05 20:05 ` Óscar Fuentes
2010-01-06 2:24 ` Stephen J. Turnbull
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=87d41okzub.fsf@kobe.laptop \
--to=keramida@ceid.upatras.gr \
--cc=angelo.graziosi@alice.it \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
/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.