From: Chong Yidong <cyd@stupidchicken.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: place to send build failure reports?
Date: Fri, 08 Aug 2008 11:58:04 -0400 [thread overview]
Message-ID: <87d4kj7b3n.fsf@stupidchicken.com> (raw)
In-Reply-To: <861w0zedev.fsf_-_@lifelogs.com> (Ted Zlatanov's message of "Fri, 08 Aug 2008 10:26:16 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> TZ> Stefan or Chong, can you suggest a place to send the build failure
> TZ> reports?
>
> Ping... The note was buried at the end of a message last time :)
I would suggest sending it to the private email of whoever volunteers to
handle this. Then, when a build fails, that volunteer would forward the
email to emacs-devel.
(The human intervention is to prevent unnecessary spam from
malfunctioning buildbots, repeated build failures during tree merges,
etc.)
next prev parent reply other threads:[~2008-08-08 15:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 22:27 eshell-defgroup. Do we really need this? Alan Mackenzie
2008-07-31 19:17 ` Ted Zlatanov
2008-07-31 19:18 ` Lennart Borgman (gmail)
2008-08-01 15:34 ` Ted Zlatanov
2008-08-01 17:08 ` Romain Francoise
2008-08-01 20:30 ` Ted Zlatanov
2008-08-02 4:18 ` Stephen J. Turnbull
2008-08-04 16:34 ` Ted Zlatanov
2008-08-04 17:49 ` Stephen J. Turnbull
2008-08-04 18:38 ` Ted Zlatanov
2008-08-05 8:20 ` Stephen J. Turnbull
2008-08-05 13:57 ` buildbots (was: eshell-defgroup. Do we really need this?) Ted Zlatanov
2008-08-05 20:25 ` Stephen J. Turnbull
2008-08-08 15:26 ` place to send build failure reports? (was: buildbots) Ted Zlatanov
2008-08-08 15:58 ` Chong Yidong [this message]
2008-08-03 19:02 ` eshell-defgroup. Do we really need this? Romain Francoise
2008-08-04 16:31 ` Ted Zlatanov
2008-08-01 16:10 ` Progress: " Alan Mackenzie
2008-08-07 19:25 ` Stefan Monnier
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=87d4kj7b3n.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.com \
/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.