Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.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: Fri, 08 Nov 2013 17:57:00 -0000	[thread overview]
Message-ID: <21117.8566.225807.905608@ruffy.mtv.corp.google.com> (raw)
In-Reply-To: <20131107190059.GA24230@host2.jankratochvil.net>

Jan Kratochvil writes:
 > On Thu, 07 Nov 2013 18:32:08 +0100, Doug Evans wrote:
 > > I don't mind such changes, but these are changes.  Agreed?
 > 
 > So far I have expexted testsuite should follow the GDB coding standards and
 > reviewers only have various reasons (*) why not to enforce the coding
 > standards so strictly (or at all) for the testsuite.

All the GDB coding standards?
The testsuite is replete with various violations.

[One might suggest requiring new tests to explicitly mark themselves
as standard-compliant or non-compliant so that we can pass the plethora
of -Wfoo that we pass for GDB.  I wouldn't disagree that that's perhaps
too much. :-)]

I don't have a strong opinion, so I'm not the one you have to convince.
[I do have a strong opinion that whatever the rules are, they be written
down of course.]

 > (*) save time of both the submitter and reviewer, making patch acceptance
 >     easier for submitters etc.
 > 
 > 
 > > I was trying to end the thread, and make some minimal mutually agreeable
 > > progress.
 > 
 > I would also like so.

I feel more comfortable getting approval for the modest changes I've proposed,
making some progress, while leaving the general discussion to another thread.
Either way is fine with me.
No one has objected to my proposal (which isn't necessarily decisive
of course).
Propose yours and see what happens (please start a separate thread though
so the Subject line is more appropriate). Being a more substantive change,
I'd feel more comfortable with explicit approval from all the GMs,
as opposed to passive non-disapproval. :-)


  reply	other threads:[~2013-11-08 17:44 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 [this message]
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=21117.8566.225807.905608@ruffy.mtv.corp.google.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --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