From: Eli Zaretskii <eliz@gnu.org>
To: Romain Francoise <romain@orebokech.com>
Cc: rudalics@gmx.at, cyd@stupidchicken.com, monnier@iro.umontreal.ca,
emacs-devel@gnu.org
Subject: Re: Bootstrapping Emacs-23.0.60-trunk newly broken (GNU/Linux, Cygwin)
Date: Sun, 13 Apr 2008 10:03:01 -0400 [thread overview]
Message-ID: <E1Jl2nN-0003ox-LQ@fencepost.gnu.org> (raw)
In-Reply-To: <87od8eje2i.fsf@elegiac.orebokech.com> (message from Romain Francoise on Sun, 13 Apr 2008 11:31:49 +0200)
> From: Romain Francoise <romain@orebokech.com>
> Date: Sun, 13 Apr 2008 11:31:49 +0200
> Cc: Chong Yidong <cyd@stupidchicken.com>,
> Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
>
> Stefan, Yidong, is it okay to send these notifications to
> emacs-devel?
I'm neither Stefan nor Yidong, but IMHO emacs-devel is the _only_
place where these notifications should go. Just be sure to subscribe
the buildbot's address to the list, because otherwise its
notifications will be held by mailman until I free them (since
emacs-devel is a moderated list), and you cannot rely on me doing that
more than once or twice a day.
Btw, aren't there facilities on Savannah (or maybe subversions) to run
scheduled builds like that? If not, IMO they should add such a
feature, and if it already exists, we should use it in preference to
external tools.
next prev parent reply other threads:[~2008-04-13 14:03 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
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 [this message]
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=E1Jl2nN-0003ox-LQ@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=romain@orebokech.com \
--cc=rudalics@gmx.at \
/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).