From: Glenn Morris <rgm@gnu.org>
To: Chong Yidong <cyd@gnu.org>
Cc: 8054@debbugs.gnu.org
Subject: bug#8054: 24.0.50; Who ever heard of a version number that doesn't change all year?
Date: Thu, 24 Nov 2011 02:06:04 -0500 [thread overview]
Message-ID: <r5r50y6lur.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87y5v63utt.fsf@gnu.org> (Chong Yidong's message of "Thu, 24 Nov 2011 14:20:30 +0800")
Chong Yidong wrote:
>> Here's a patch to define an `emacs-bzr-version' during dumping and
>> include it in bug reports.
>
> I think this would need the branch name too, in order to be useful.
Really? At present, emacs-bzr-version will contain something like:
106501 rgm@gnu.org-20111124035909-rx8lttx9f1j29t69
So it's not just a revision number. The second bit is "a globally unique
identifier for the revision so that it can be referred to without
ambiguity".
But it's trivial to add eg parent_location from branch.conf, if you
really think this is necessary.
next prev parent reply other threads:[~2011-11-24 7:06 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
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 [this message]
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=r5r50y6lur.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=8054@debbugs.gnu.org \
--cc=cyd@gnu.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).