From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Tom Tromey <tromey@redhat.com>,
gdb-patches <gdb-patches@sourceware.org>,
Pedro Alves <palves@redhat.com>,
Stan Shebs <stan@codesourcery.com>
Subject: Re: [PATCH] Fix Gold/strip discrepancies for PR 11786
Date: Tue, 12 Nov 2013 19:58:00 -0000 [thread overview]
Message-ID: <20131112184556.GA20259@host2.jankratochvil.net> (raw)
In-Reply-To: <CADPb22QadnmVhw6oQMGm3Gg8qYwuGucypocX_ZfwGzfp5AJ5TA@mail.gmail.com>
On Tue, 12 Nov 2013 19:33:33 +0100, Doug Evans wrote:
> https://sourceware.org/gdb/wiki/Internals%20GDB-Testsuite-Coding-Standards
>
> Feel free to tweak or add whatever community rules there are.
> I'll add more as it occurs to me.
FYI I find
In C code, don't use K&R function definitions
redundant against the part above
The best guidance one can give is that unless a test requires
a particular style (which is rare) you can't go wrong following the
GDB coding standards.
but it is OK even as a redundant text.
Jan
next prev parent reply other threads:[~2013-11-12 18:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 23:26 Doug Evans
2013-10-30 23:57 ` Doug Evans
2013-10-31 16:42 ` Jan Kratochvil
2013-11-04 22:38 ` Doug Evans
2013-11-04 23:04 ` Cary Coutant
2013-11-05 3:42 ` Tom Tromey
2013-11-05 17:22 ` Doug Evans
2013-11-05 17:23 ` Jan Kratochvil
2013-11-05 18:01 ` Doug Evans
2013-11-05 18:13 ` Jan Kratochvil
2013-11-06 21:16 ` Doug Evans
2013-11-06 21:28 ` Jan Kratochvil
2013-11-07 1:05 ` Stan Shebs
2013-11-07 18:01 ` Doug Evans
2013-11-07 19:03 ` Jan Kratochvil
2013-11-08 17:57 ` Doug Evans
2013-11-08 19:17 ` Jan Kratochvil
2013-11-12 18:46 ` Doug Evans
2013-11-12 19:58 ` Jan Kratochvil [this message]
2013-11-12 22:05 ` Doug Evans
2013-11-05 17:32 ` Tom Tromey
2013-11-05 17:32 ` Pedro Alves
2013-11-05 17:04 ` Jan Kratochvil
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=20131112184556.GA20259@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=stan@codesourcery.com \
--cc=tromey@redhat.com \
/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