From: Chong Yidong <cyd@gnu.org>
To: Roland Winkler <winkler@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs pretest 24.2.90
Date: Tue, 27 Nov 2012 12:07:24 +0800 [thread overview]
Message-ID: <87624rpu2r.fsf@gnu.org> (raw)
In-Reply-To: <87sj7xwt5o.fsf@gnu.org> (Roland Winkler's message of "Sun, 25 Nov 2012 10:20:51 -0600")
Roland Winkler <winkler@gnu.org> writes:
> Yet I was wondering: what information is generally useful here to
> characterize "one's build platform"? I copied some information from
> buffers created via `report-emacs-bug' - obviously a clumsy
> procedure.
You can insert the Emacs version at point with C-u M-x emacs-version RET
next prev parent reply other threads:[~2012-11-27 4:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 16:13 Emacs pretest 24.2.90 Chong Yidong
2012-11-24 17:01 ` Eli Zaretskii
2012-11-25 16:20 ` Roland Winkler
2012-11-27 4:07 ` Chong Yidong [this message]
2012-11-27 4:13 ` Drew Adams
2012-11-27 13:34 ` Roland Winkler
2012-11-27 14:53 ` Eli Zaretskii
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=87624rpu2r.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=winkler@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).