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>
Subject: Re: [PATCH] Fix Gold/strip discrepancies for PR 11786
Date: Wed, 06 Nov 2013 21:28:00 -0000 [thread overview]
Message-ID: <20131106212434.GA4193@host2.jankratochvil.net> (raw)
In-Reply-To: <CADPb22S4ivEm=abcrxLBQwiB9yrB7CryvOBNi+rh-GdOpek5nQ@mail.gmail.com>
On Wed, 06 Nov 2013 22:14:27 +0100, Doug Evans wrote:
> It will basically say tests are in general not required to following
> the GDB coding standards,
What is the reason for it?
I would find more logical to say tests should follow the same rules as GDB
code, unless there is a specific reason for it. Such as importing an existing
external reproducer, machine generated output etc.
If GDB coding standards are not acceptable for testcases then it looks to me
as an indication the GDB coding standards should be changed.
Jan
next prev parent reply other threads:[~2013-11-06 21:24 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 [this message]
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
2013-11-12 22:05 ` Doug Evans
2013-11-05 17:32 ` Pedro Alves
2013-11-05 17:32 ` Tom Tromey
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=20131106212434.GA4193@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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