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] gdb/riscv: Remove 'Contributed by....' comments
Date: Tue, 06 Mar 2018 20:30:00 -0000 [thread overview]
Message-ID: <c9486dfe2753a3a9683dbb131ecfb4f5808a27c1@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT c9486dfe2753a3a9683dbb131ecfb4f5808a27c1 ***
Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: c9486dfe2753a3a9683dbb131ecfb4f5808a27c1
gdb/riscv: Remove 'Contributed by....' comments
The GDB coding standard states these lines should never have been
added.
gdb/ChangeLog:
* riscv-tdep.c: Remove 'Contributed by ...' lines from header
comment.
* riscv-tdep.h: Likewise.
next reply other threads:[~2018-03-06 20:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 20:30 sergiodj+buildbot [this message]
2018-03-06 20:30 ` Failures on Debian-s390x-m64, branch master sergiodj+buildbot
2018-03-06 20:31 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-03-06 20:38 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-03-06 20:43 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-03-06 20:45 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-03-06 20:59 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-03-06 21:03 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-03-06 21:07 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-03-06 23:00 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-03-06 23:26 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-03-07 17:13 ` Failures on Ubuntu-AArch64-native-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=c9486dfe2753a3a9683dbb131ecfb4f5808a27c1@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).