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] Update my email address. Date: Tue, 03 Oct 2017 21:48:00 -0000 [thread overview] Message-ID: <c0107b0f57bc958b640dabafd4c6c618ea023397@gdb-build> (raw) *** TEST RESULTS FOR COMMIT c0107b0f57bc958b640dabafd4c6c618ea023397 *** Author: Jim Wilson <jim.wilson@linaro.org> Branch: master Commit: c0107b0f57bc958b640dabafd4c6c618ea023397 Update my email address. sim/ * MAINTAINERS (aarch64): Update my email address.
next reply other threads:[~2017-10-03 21:48 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-03 21:48 sergiodj+buildbot [this message] 2017-10-03 21:48 ` Failures on Fedora-x86_64-m64, branch master sergiodj+buildbot 2017-10-03 21:50 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-10-03 21:50 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-10-03 21:59 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2017-10-03 22:01 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-10-03 22:02 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-10-03 22:06 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-10-03 22:09 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-10-03 22:17 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2017-10-03 22:30 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-10-03 22:54 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot -- strict thread matches above, loose matches on Subject: below -- 2019-02-23 1:12 [binutils-gdb] Update my email address sergiodj+buildbot 2018-03-14 13:59 sergiodj+buildbot 2017-10-05 4:45 sergiodj+buildbot 2015-06-29 9:46 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=c0107b0f57bc958b640dabafd4c6c618ea023397@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: linkBe 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).