public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: overseers@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>, builder@sourceware.org
Subject: Re: ☺ Buildbot (GNU Toolchain): sourceware-reconfig - build successful (main)
Date: Mon, 2 May 2022 17:25:42 +0200 (CEST)	[thread overview]
Message-ID: <0f0d985e-e6c3-3931-c65a-08a1ba4a4fcc@pfeifer.com> (raw)
In-Reply-To: <20220428144258.5A92F3856257@sourceware.org>

On Thu, 28 Apr 2022, builder--- via Overseers wrote:
> A passing build has been detected on builder sourceware-reconfig while 
> building sourceware.
> 
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#builders/60/builds/35

I'm wondering - should these really go to overseers@?

(This is less about me, I just put in a mail filter, more a general
question.)

Gerald

  reply	other threads:[~2022-05-02 15:25 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 14:42 builder
2022-05-02 15:25 ` Gerald Pfeifer [this message]
2022-05-02 15:29   ` Frank Ch. Eigler
  -- strict thread matches above, loose matches on Subject: below --
2022-05-25 14:51 builder
2022-05-25 14:45 builder
2022-05-02 11:42 builder
2022-05-01 19:03 builder
2022-05-01  1:21 builder
2022-05-01  1:15 builder
2022-04-30 22:18 builder
2022-04-30 22:09 builder
2022-04-29 21:24 builder
2022-04-29 16:54 builder
2022-04-29  9:42 builder
2022-04-29  1:36 builder
2022-04-29  1:15 builder
2022-04-29  1:09 builder
2022-04-28 18:15 builder
2022-04-28 16:27 builder
2022-04-28 15:39 builder
2022-04-28 14:00 builder
2022-04-28 11:39 builder
2022-04-28 11:18 builder
2022-04-27 15:00 builder
2022-04-26 22:30 builder
2022-04-26 17:30 builder
2022-04-26 17:30 builder
2022-04-26 11:03 builder
2022-04-26  1:21 builder
2022-04-25 22:03 builder
2022-04-25 17:54 builder
2022-04-25 17:42 builder
2022-04-25 17:27 builder
2022-04-25 17:18 builder
2022-04-25 14:48 builder
2022-04-25 13:39 builder
2022-04-25 12:30 builder
2022-04-25 10:39 builder
2022-04-25 10:24 builder
2022-04-25  9:06 builder
2022-04-24 20:00 builder
2022-04-24 19:42 builder
2022-04-23 14:51 builder
2022-04-22 15:45 builder
2022-04-22  1:00 builder
2022-04-22  0:15 builder
2022-04-21 19:32 builder
2022-04-18 22:38 builder
2022-04-18 21:44 builder

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=0f0d985e-e6c3-3931-c65a-08a1ba4a4fcc@pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=builder@sourceware.org \
    --cc=mark@klomp.org \
    --cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).