From: "Roland Winkler" <winkler@gnu.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Chong Yidong' <cyd@gnu.org>, emacs-devel@gnu.org
Subject: RE: Emacs pretest 24.2.90
Date: Tue, 27 Nov 2012 07:34:22 -0600 [thread overview]
Message-ID: <20660.49502.56966.512844@gargle.gargle.HOWL> (raw)
In-Reply-To: <9729A6E854424176B65340F2406C210B@us.oracle.com>
On Mon Nov 26 2012 Drew Adams wrote:
> > > 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
>
> I too have sometimes used `report-emacs-bug', just to get the
> complete version info. Perhaps `C-u C-u' with `emacs-version'
> could provide that info?
>
> I'm talking about the difference between these two (the first is from
> `report-emacs-bug', and provides more info about the build):
My question is first: what information is possibly relevant or
helpful here?
I thought that the main purpose of emacs-version was to distinguish
the different (historical) versions of emacs. During the pretest of
a particular emacs version, this might not provide too much variety.
I guess under GNU linux the most basic information about the build
platform is provided by "lsb_release -d". report-emacs-bug includes
the output of this command.
But again: I don't know what is possibly most useful during a pretest.
next prev parent reply other threads:[~2012-11-27 13:34 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
2012-11-27 4:13 ` Drew Adams
2012-11-27 13:34 ` Roland Winkler [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20660.49502.56966.512844@gargle.gargle.HOWL \
--to=winkler@gnu.org \
--cc=cyd@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@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 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.