From: Lennart Borgman <lennart.borgman@gmail.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 8054@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#8054: 24.0.50; Who ever heard of a version number that doesn't change all year?
Date: Sat, 19 Feb 2011 23:22:06 +0100 [thread overview]
Message-ID: <AANLkTin9-7zb1x5+RJd3q7odfWxMk=PkyACH1V+BEYgi@mail.gmail.com> (raw)
In-Reply-To: <87vd0fvfi5.fsf@stupidchicken.com>
On Sat, Feb 19, 2011 at 11:14 PM, Chong Yidong <cyd@stupidchicken.com> wrote:
> Lennart Borgman <lennart.borgman@gmail.com> writes:
>
>> On Wed, Feb 16, 2011 at 1:54 PM, <jidanni@jidanni.org> wrote:
>>> Gentlemen, let's face it, your version number,
>>> emacs-version "24.0.50.1"
>>> is a total disaster for use in e.g., report-emacs-bug.
>>
>> Yepp. I have suggested to use bzr ids instead. Which is what I am
>> using in my patched version of EmacsW32 (so I have some code for w32
>> for it).
>>
>> I think this should be added to the makefiles.
>
> It would be rather annoying to change version.el or other working file
> everything we make a bzr commit, so that's not a good idea.
>
> What we could do is to check if Emacs is being run from inside a bzr
> working directory bound to a savannah.gnu.org location (e.g. trunk), and
> use vc-bzr-current-revision to find and report that revision number.
Yes, something like that is what I have in mind.
> But such a feature would be pretty limited: it would not apply to anyone
> working in a feature branch,
Of course it should be extended to that.
> nor would it apply to those running a "make
> install"ed Emacs.
Why not?
next prev parent reply other threads:[~2011-02-19 22:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <handler.8054.D8054.133382844412487.notifdone@debbugs.gnu.org>
2011-02-16 12:54 ` bug#8054: 24.0.50; Who ever heard of a version number that doesn't change all year? jidanni
2011-02-16 13:10 ` Lennart Borgman
2011-02-19 22:14 ` Chong Yidong
2011-02-19 22:22 ` Lennart Borgman [this message]
2011-02-19 22:23 ` Chong Yidong
2011-02-19 22:35 ` Lennart Borgman
2011-11-22 0:48 ` Glenn Morris
2011-11-23 13:03 ` Juanma Barranquero
2011-11-23 13:24 ` Christoph Scholtes
2012-04-07 19:53 ` Glenn Morris
2011-11-23 13:37 ` Lennart Borgman
2011-11-24 6:20 ` Chong Yidong
2011-11-24 7:06 ` Glenn Morris
2011-02-26 3:04 ` debbugs-submit-bounces
2011-02-26 3:51 ` Glenn Morris
2012-04-13 0:26 ` bug#8054: closed (Re: bug#8054: 24.0.50; Who ever heard of a version number that doesn't change all year?) jidanni
2012-04-13 3:00 ` Glenn Morris
2012-04-13 18:48 ` bug#8054: 24.0.50; Who ever heard of a version number that doesn't change all year? jidanni
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='AANLkTin9-7zb1x5+RJd3q7odfWxMk=PkyACH1V+BEYgi@mail.gmail.com' \
--to=lennart.borgman@gmail.com \
--cc=8054@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=jidanni@jidanni.org \
/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).