public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Add myself to gdb/MAINTAINERS
Date: Mon, 01 Apr 2019 08:41:00 -0000 [thread overview]
Message-ID: <8828efdb24ef337e074183a0db3ac6399a3c09ba@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 8828efdb24ef337e074183a0db3ac6399a3c09ba ***
Author: Marco Barisione <mbarisione@undo.io>
Branch: master
Commit: 8828efdb24ef337e074183a0db3ac6399a3c09ba
Add myself to gdb/MAINTAINERS
gdb/ChangeLog:
2019-04-01 Marco Barisione <mbarisione@undo.io>
* MAINTAINERS (Write After Approval): Add Marco Barisione.
next reply other threads:[~2019-04-01 8:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 8:41 sergiodj+buildbot [this message]
2019-04-01 10:06 ` Failures on Debian-s390x-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2019-04-03 21:26 ` Failures on Fedora-i686, " sergiodj+buildbot
2019-04-03 21:43 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2019-04-03 21:53 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2019-04-03 22:32 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2019-04-03 23:04 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2019-04-08 15:26 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2019-04-12 14:39 ` *** COMPILATION FAILED *** Failures on NetBSD-x86_64-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2019-05-17 10:06 [binutils-gdb] Add myself to gdb/MAINTAINERS sergiodj+buildbot
2020-01-01 21:02 gdb-buildbot
2020-01-03 8:37 gdb-buildbot
2020-05-03 18:02 gdb-buildbot
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=8828efdb24ef337e074183a0db3ac6399a3c09ba@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--cc=gdb-testers@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).