From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Juanma Barranquero" <lekktu@gmail.com>,
"Angelo Graziosi" <angelo.graziosi@alice.it>,
"Eli Zaretskii" <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Bootstrapping Emacs-23.0.60-trunk newly broken (GNU/Linux, Cygwin)
Date: Sat, 12 Apr 2008 14:12:51 +0200 [thread overview]
Message-ID: <f7ccd24b0804120512w28dd704fye0bd4f6528d8f058@mail.gmail.com> (raw)
In-Reply-To: <87d4ovl2id.fsf@elegiac.orebokech.com>
On Sat, Apr 12, 2008 at 1:46 PM, Romain Francoise <romain@orebokech.com> wrote:
> While that is certainly true, it's also a waste of time for our
> users to have to report bugs that could be avoided, and a waste of
> our own time because we have to handle the reports.
>
> For the last few months I've been running a buildbot for the trunk
> and the 22 branch (and before the merge, for the unicode branch), it
> does a clean build every night (on GNU/Linux only) and usually
> catches bootstrap failures. See <URL:http://build.orebokech.com/>.
Having an automatic method of detecting bootstrap failures (and
reporting to the committer(s)) would be good IMHO. Still, that does
not change the previous point: those building from the trunk should
know to expect trouble (and not just from building/bootstrapping)
every now and then.
Juanma
next prev parent reply other threads:[~2008-04-12 12:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 9:06 Bootstrapping Emacs-23.0.60-trunk still fails (GNU/Linux, Cygwin) Angelo Graziosi
2008-04-12 7:45 ` Bootstrapping Emacs-23.0.60-trunk newly broken " Angelo Graziosi
2008-04-12 8:30 ` Eli Zaretskii
2008-04-12 9:18 ` Angelo Graziosi
2008-04-12 9:27 ` Juanma Barranquero
2008-04-12 11:46 ` Romain Francoise
2008-04-12 12:12 ` Juanma Barranquero [this message]
2008-04-12 12:16 ` martin rudalics
2008-04-12 13:41 ` Romain Francoise
2008-04-12 12:53 ` martin rudalics
2008-04-13 9:31 ` Romain Francoise
2008-04-13 14:03 ` Eli Zaretskii
2008-04-14 0:52 ` Richard Stallman
2008-04-12 13:45 ` Stefan Monnier
2008-04-12 14:06 ` Jason Rumney
2008-04-12 14:24 ` Eric Hanchrow
2008-04-12 10:08 ` Eli Zaretskii
2008-04-12 9:28 ` 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=f7ccd24b0804120512w28dd704fye0bd4f6528d8f058@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=angelo.graziosi@alice.it \
--cc=eliz@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).