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] MAINTAINERS: Update my company e-mail address
Date: Mon, 22 Jan 2018 15:56:00 -0000 [thread overview]
Message-ID: <d65ce302abcb260e14ca5f201b78e8e6d4a2e720@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT d65ce302abcb260e14ca5f201b78e8e6d4a2e720 ***
Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: d65ce302abcb260e14ca5f201b78e8e6d4a2e720
MAINTAINERS: Update my company e-mail address
Following my recent transition from Imagination Technologies to the
reincarnated MIPS company update MAINTAINERS entries accordingly.
binutils/
* MAINTAINERS: Update my company e-mail address.
gdb/
* MAINTAINERS: Update my company e-mail address.
sim/
* MAINTAINERS: Update my company e-mail address.
next reply other threads:[~2018-01-22 15:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 15:56 sergiodj+buildbot [this message]
2018-01-22 15:56 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-01-22 15:57 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-01-22 16:03 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-01-22 16:11 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-01-22 16:14 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-01-22 16:24 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-01-22 16:28 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-01-22 16:35 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-01-22 16:49 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-01-22 21:59 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2018-01-23 1:15 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-23 2:19 ` Failures on Ubuntu-AArch32-m32, " sergiodj+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=d65ce302abcb260e14ca5f201b78e8e6d4a2e720@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).