From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: Ken Raeburn <raeburn@raeburn.org>,
"emacs-devel@gnu.org discussions" <emacs-devel@gnu.org>
Subject: Re: next emacs version?
Date: Tue, 23 Mar 2010 11:05:52 +0900 [thread overview]
Message-ID: <87aatziygv.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <e01d8a51003191939t54b655c6t5aee1c414bbb63f4@mail.gmail.com>
Lennart Borgman writes:
> On Sat, Mar 20, 2010 at 3:35 AM, Ken Raeburn <raeburn@raeburn.org> wrote:
> >
> > Unless you want to start putting bzr revision numbers into the emacs version string (which I think is a bad idea), that's going to be the case.
>
> But perhaps having the bzr version available in another variable in
> the build Emacs would be a good idea?
There is no such thing as *the* bzr revision number, because (a)
revision numbers are supposed to be ordered, but revision numbers on
parallel branches cannot be ordered, and (b) revision numbers are not
consistent across repositories.
It is a good idea to put in the revision ID in a variable (SHA1s are
barely tolerable in the version string because of their length, but
bzr revision IDs can be much longer), but revision IDs aren't ordered,
either.
This is not useful for Drew, though.
next prev parent reply other threads:[~2010-03-23 2:05 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 11:23 next emacs version? Drew Adams
2010-03-19 13:22 ` Eli Zaretskii
2010-03-19 17:29 ` Drew Adams
2010-03-19 18:09 ` Eli Zaretskii
2010-03-19 18:46 ` Drew Adams
2010-03-19 19:02 ` Eli Zaretskii
2010-03-19 20:02 ` Drew Adams
2010-03-19 21:15 ` Eli Zaretskii
2010-03-19 21:23 ` Drew Adams
2010-03-20 2:35 ` Ken Raeburn
2010-03-20 2:39 ` Lennart Borgman
2010-03-20 3:42 ` Óscar Fuentes
2010-03-20 15:51 ` Lennart Borgman
2010-03-20 5:31 ` Ken Raeburn
2010-03-23 2:05 ` Stephen J. Turnbull [this message]
2010-03-20 3:38 ` Drew Adams
2010-03-20 5:31 ` Ken Raeburn
2010-03-20 6:51 ` Drew Adams
2010-03-20 5:31 ` Ken Raeburn
2010-03-20 6:51 ` Drew Adams
2010-03-23 2:34 ` Stephen J. Turnbull
2010-03-23 5:01 ` Miles Bader
2010-03-23 5:39 ` Drew Adams
2010-03-20 3:51 ` Jason Rumney
2010-03-20 6:47 ` Drew Adams
2010-03-20 8:39 ` Eli Zaretskii
2010-03-20 14:58 ` Drew Adams
2010-03-20 16:22 ` Eli Zaretskii
2010-03-20 8:11 ` Eli Zaretskii
2010-03-19 20:55 ` Stefan Monnier
2010-03-19 21:16 ` Drew Adams
2010-03-20 19:10 ` Stefan Monnier
2010-03-20 20:29 ` Drew Adams
2010-03-20 21:53 ` Stefan Monnier
2010-03-20 23:09 ` Drew Adams
2010-03-20 23:26 ` Drew Adams
2010-03-22 1:22 ` Stefan Monnier
2010-03-22 7:22 ` Drew Adams
2010-03-22 13:52 ` Stefan Monnier
2010-03-21 21:34 ` Thien-Thi Nguyen
2010-03-21 23:20 ` Drew Adams
2010-03-19 14:52 ` Chong Yidong
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=87aatziygv.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=raeburn@raeburn.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).