all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Angelo Graziosi <angelo.graziosi@alice.it>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: Emacs <emacs-devel@gnu.org>
Subject: Re: A little suggestion
Date: Tue, 05 Jan 2010 12:05:22 +0100	[thread overview]
Message-ID: <4B431CF2.4080408@alice.it> (raw)
In-Reply-To: <e01d8a51001050240q7c1c7b69m833930f0f4989677@mail.gmail.com>

Il 05/01/2010 11.40, Lennart Borgman ha scritto:
> 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.

Shouldn't writing 'rev. 99259' in some .bzr files be enough? For 
example, when building, if it finds 'rev. 99259', it generates:

"GNU Emacs 23.1.91.1 rev. 99259..."

else if it finds 'release', it gives:

"GNU Emacs 23.2 release..."

I am sure Emacs guys have better ideas. :-)


Thanks,
Angelo.





  reply	other threads:[~2010-01-05 11:05 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 [this message]
2010-01-05 11:15   ` Sven Joachim
2010-01-05 21:26   ` Giorgos Keramidas
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=4B431CF2.4080408@alice.it \
    --to=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.