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] AOUT/COFF/PE messages Date: Mon, 26 Feb 2018 01:03:00 -0000 [thread overview] Message-ID: <59d08d6ce8cb6c41691266e133304c961c270e85@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 59d08d6ce8cb6c41691266e133304c961c270e85 *** Author: Alan Modra <amodra@gmail.com> Branch: master Commit: 59d08d6ce8cb6c41691266e133304c961c270e85 AOUT/COFF/PE messages Capitalization, full-stops and unnecessary trailing \n fixes. * aout-adobe.c, * aout-cris.c, * i386linux.c, * m68klinux.c, * sparclinux.c, * coff-alpha.c, * coff-arm.c, * coff-mcore.c, * coffcode.h, * coffgen.c, * cofflink.c, * ecoff.c, * pe-mips.c, * peXXigen.c, * peicode.h: Standardize error/warning messages.
next reply other threads:[~2018-02-26 1:03 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-02-26 1:03 sergiodj+buildbot [this message] 2018-02-26 1:03 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-02-26 4:07 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-02-26 4:11 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-02-26 4:28 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-02-26 4:35 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-02-26 10:36 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-02-26 11:28 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-02-26 12:21 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2018-03-01 0:21 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-03-01 0:37 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " 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=59d08d6ce8cb6c41691266e133304c961c270e85@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).