unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Roland Winkler <winkler@gnu.org>
To: Chong Yidong <cyd@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs pretest 24.2.90
Date: Sun, 25 Nov 2012 10:20:51 -0600	[thread overview]
Message-ID: <87sj7xwt5o.fsf@gnu.org> (raw)
In-Reply-To: <87ehjjgerp.fsf@gnu.org> (Chong Yidong's message of "Sun, 25 Nov 2012 00:13:46 +0800")

On Sat, Nov 24 2012, Chong Yidong wrote:
> Please send me an email reporting success or failure on your build
> platform.

I compiled Emacs successfully on the two systems described below. 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. Could it
facilitate this process if there was a command `report-emacs-build' that
gathers the relevant information in a mail buffer, similar to
`report-emacs-bug'?
Possibly, a command `report-emacs-build-success' was really sufficient,
because build failures most often might deserve a bug report.


In GNU Emacs 24.2.90.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.20.1)
 of 2012-11-24 on regnitz
Windowing system distributor `The X.Org Foundation', version 11.0.10706000
System Description:	Ubuntu 10.04.4 LTS

In GNU Emacs 24.2.90.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.12.9)
 of 2012-11-24 on lukas
System Description:     Ubuntu 8.04.4 LTS



  parent reply	other threads:[~2012-11-25 16:20 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 [this message]
2012-11-27  4:07   ` Chong Yidong
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=87sj7xwt5o.fsf@gnu.org \
    --to=winkler@gnu.org \
    --cc=cyd@gnu.org \
    --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 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).