Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [GDB BuildBot] New "Try Server"
Date: Tue, 20 Sep 2016 20:20:00 -0000	[thread overview]
Message-ID: <87wpi6gwdm.fsf@redhat.com> (raw)
In-Reply-To: <8760rpef2m.fsf@redhat.com> (Sergio Durigan Junior's message of	"Thu, 28 Jul 2016 15:29:53 -0400")

[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]

On Thursday, July 28 2016, I wrote:

> Hi there,

Hi again,

I've now updated the wiki page with instructions on the "Try" scheduler:

  <https://sourceware.org/gdb/wiki/BuildBot#Try_Jobs>

It's basically a copy-and-paste of my first e-mail, but a few things
have changed:

1) From now on, I will provide access to our Try scheduler to anyone who
has commit access to the official GDB repository.  I've decided to lift
the initial restrictions because I think they're too strict.

2) I've also added a bunch of new builders to the list of supported
builders for the Try scheduler.  Take a look at
<https://sourceware.org/gdb/wiki/BuildBot#Available_Builders> to see the
current list.

I was also noticing a few problems with e-mail notifications for the Try
scheduler, but these should be fixed now.

Let me know if you have any questions, comments or suggestions!

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

      parent reply	other threads:[~2016-09-20 20:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28 19:30 Sergio Durigan Junior
2016-07-29 11:53 ` Antoine Tremblay
2016-07-29 15:40   ` Sergio Durigan Junior
2016-07-29 17:00     ` Antoine Tremblay
2016-09-20 20:20 ` Sergio Durigan Junior [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=87wpi6gwdm.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@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