public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj@redhat.com To: gdb-testers@sourceware.org Subject: Test results for commit 9f04ac5f92a1efc97b38cb6560fc10146fad64b6 on branch master Date: Fri, 13 Feb 2015 11:32:00 -0000 [thread overview] Message-ID: <9f04ac5f92a1efc97b38cb6560fc10146fad64b6@kwanyin> (raw) *** TEST RESULTS FOR COMMIT 9f04ac5f92a1efc97b38cb6560fc10146fad64b6 *** Author: Yao Qi <yao.qi@arm.com> Branch: master Commit: 9f04ac5f92a1efc97b38cb6560fc10146fad64b6 Update Yao Qi's email address in MAINTAINERS gdb: * MAINTAINERS: Update my email address.
next reply other threads:[~2015-02-13 11:14 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-13 11:32 sergiodj [this message] 2015-02-13 11:35 ` Failures on Fedora-ppc64be-m64, " sergiodj 2015-02-13 11:39 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj 2015-02-13 11:49 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj 2015-02-13 11:54 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj 2015-02-13 12:02 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj 2015-02-13 12:02 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj 2015-02-13 12:19 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj 2015-02-13 12:40 ` Failures on Fedora-ppc64le-m64, " sergiodj 2015-02-13 13:22 ` Failures on Fedora-x86_64-m32, " sergiodj 2015-02-13 13:41 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj 2015-02-13 14:09 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj 2015-02-13 14:10 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj 2015-02-14 17:57 ` Failures on Debian-i686, " sergiodj 2015-02-14 21:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj
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=9f04ac5f92a1efc97b38cb6560fc10146fad64b6@kwanyin \ --to=sergiodj@redhat.com \ --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).