From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: buildbot failure in Gnus on xemacs21.4-linux
Date: Fri, 08 Jul 2011 14:18:55 +0200 [thread overview]
Message-ID: <m262nddky8.fsf@ibookg4-c2.pc.gwdg.de> (raw)
In-Reply-To: <b4miprdhf7e.fsf@jpl.org> (Katsumi Yamaoka's message of "Fri, 08 Jul 2011 07:57:09 +0900")
Katsumi Yamaoka writes:
> Are the gnus-buildbot mail sent to also the author, not only the
> committer? If not, I hope those are done so.
Only the committer gets the mails; it used to be the author, but I
changed it because when authors commit to the Emacs trunk, they're
usually not terribly interested in stuff like XEmacs compatibility, so I
think that work is primarily on us. Also, most of the compiler warnings
so far were spurious and had to be dealt with in the Gnus trunk
(dgnushack.el or lpath.el), and the author might not have access to it
or isn't familiar with the process.
So far I've been unsuccessful to add author and committer to the
blamelist, since in Buildbot it seems there's always exactly *one*
person responsible for a change. But I will ask on the Buildbot
mailinglist.
-David
prev parent reply other threads:[~2011-07-08 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Qepcx-0007Mp-0v@v3-1008.vxen.de>
2011-07-07 22:57 ` Katsumi Yamaoka
2011-07-08 0:57 ` Daiki Ueno
2011-07-08 12:18 ` David Engster [this message]
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=m262nddky8.fsf@ibookg4-c2.pc.gwdg.de \
--to=deng@randomsample.de \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).