From: Lennart Borgman <lennart.borgman@gmail.com>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: next emacs version?
Date: Sat, 20 Mar 2010 16:51:03 +0100 [thread overview]
Message-ID: <e01d8a51003200851w789e6702iaa0695221d4fc16e@mail.gmail.com> (raw)
In-Reply-To: <87vdcrhd55.fsf@telefonica.net>
On Sat, Mar 20, 2010 at 4:42 AM, Óscar Fuentes <ofv@wanadoo.es> wrote:
> Lennart Borgman <lennart.borgman@gmail.com> writes:
>
>>> 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?
>
> It would be useful to include bzr's revision id (not revision number)
> along the info sent by M-x report-emacs-bug.
I suggest that something like this is used to get the info
bzr version-info --custom --template "(defconst
emacs-bzr-revision-id \"{revision_id}\")"
bzr version-info --custom --template "(defconst emacs-bzr-date \"{date}\")"
bzr version-info --custom --template "(defconst emacs-bzr-revno {revno})"
bzr version-info --custom --template "(defconst
emacs-bzr-branch-nick \"{branch_nick}\")"
and the output is put in a file emacs-bzr-id.el that is loaded at startup.
next prev parent reply other threads:[~2010-03-20 15:51 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 [this message]
2010-03-20 5:31 ` Ken Raeburn
2010-03-23 2:05 ` Stephen J. Turnbull
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e01d8a51003200851w789e6702iaa0695221d4fc16e@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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.