From: "Frank Ch. Eigler via Gdb" <gdb@sourceware.org>
To: Luis Machado <luis.machado@arm.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>,
Overseers mailing list <overseers@sourceware.org>,
Mark Wielaard <mark@klomp.org>,
binutils@sourceware.org
Subject: Re: Adding binutils to the GNU Toolchain buildbot on sourceware
Date: Mon, 25 Apr 2022 08:30:30 -0400 [thread overview]
Message-ID: <YmaUZsm4BAQnTPem@elastic.org> (raw)
In-Reply-To: <5c1f217a-109c-2973-6c69-abf412133dee@arm.com>
Hi -
> An additional buildbot job for gdb/gdbserver would be fine. It's just that a
> single build for everything is simpler, in my opinion.
Yes, that would be interesting.
> Is the idea to revive the old buildbot we had for GDB, but for binutils?
We're welcoming the gdb project on the new buildbot server. Just need
to set up some workers from the community.
- FChE
next prev parent reply other threads:[~2022-04-25 12:31 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YmZkKRO+yUHeFqV0@wildebeest.org>
2022-04-25 10:37 ` Luis Machado via Gdb
2022-04-25 10:43 ` Frank Ch. Eigler via Gdb
2022-04-25 12:16 ` Luis Machado via Gdb
2022-04-25 12:30 ` Frank Ch. Eigler via Gdb [this message]
2022-04-25 18:20 ` Mark Wielaard
2022-04-25 18:27 ` Frank Ch. Eigler via Gdb
2022-04-25 22:11 ` Mark Wielaard
2022-04-26 3:33 ` Alan Modra via Gdb
2022-04-26 6:22 ` Jan Beulich via Gdb
2022-04-26 12:27 ` Nick Clifton via Gdb
2022-04-26 13:49 ` Jan Beulich via Gdb
2022-04-26 15:47 ` H.J. Lu via Gdb
2022-04-27 6:15 ` Jan Beulich via Gdb
2022-04-28 12:10 ` Nick Clifton via Gdb
2022-04-28 13:07 ` Jan Beulich via Gdb
2022-04-26 15:54 ` H.J. Lu via Gdb
2022-04-26 23:33 ` Alan Modra via Gdb
2022-04-27 18:32 ` [PATCH] x86: Disable 2 tests with large memory requirement H.J. Lu via Gdb
2022-04-26 7:01 ` Adding binutils to the GNU Toolchain buildbot on sourceware Luis Machado via Gdb
2022-04-26 9:40 ` Frank Ch. Eigler via Gdb
2022-04-26 22:59 ` Mark Wielaard
2022-04-26 22:34 ` Mark Wielaard
2022-04-28 12:23 ` Luis Machado via Gdb
2022-04-28 13:50 ` Frank Ch. Eigler via Gdb
2022-04-28 13:53 ` Luis Machado via Gdb
2022-04-28 14:22 ` Frank Ch. Eigler via Gdb
2022-04-28 17:04 ` Mark Wielaard
2022-04-28 14:48 ` Mark Wielaard
2022-04-28 14:19 ` Mark Wielaard
2022-04-28 14:47 ` Thomas Fitzsimmons
2022-04-28 16:28 ` Mark Wielaard
2022-04-29 20:04 ` gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) Mark Wielaard
2022-05-01 19:44 ` Mark Wielaard
2022-05-03 15:41 ` Simon Marchi via Gdb
2022-05-13 8:21 ` Mark Wielaard
2022-04-28 17:50 ` Adding binutils to the GNU Toolchain buildbot on sourceware Nick Alcock via Gdb
2022-04-29 17:54 ` Mark Wielaard
2022-04-30 0:12 ` Nick Alcock via Gdb
2022-04-30 22:27 ` Mark Wielaard
2022-05-03 12:48 ` Nick Alcock via Gdb
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=YmaUZsm4BAQnTPem@elastic.org \
--to=gdb@sourceware.org \
--cc=binutils@sourceware.org \
--cc=fche@elastic.org \
--cc=luis.machado@arm.com \
--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