Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Pedro Alves <palves@redhat.com>
Cc: Gary Benson <gbenson@redhat.com>,
	gdb-patches <gdb-patches@sourceware.org>,
		Tom Tromey <tromey@redhat.com>
Subject: Re: [PATCH 1/3 v4] Introduce common/errors.h
Date: Tue, 29 Jul 2014 16:44:00 -0000	[thread overview]
Message-ID: <CADPb22Rrkahzsj388P22Tsj3xdVDhrBBJVSCJNVJO0xBGGRPkQ@mail.gmail.com> (raw)
In-Reply-To: <53D2438C.8040009@redhat.com>

On Fri, Jul 25, 2014 at 4:46 AM, Pedro Alves <palves@redhat.com> wrote:
>> Yes, eventually.  I plan to submit an initial series, in which
>> common-defs.h only includes the two config.h files, and any files
>> not including either defs.h or server.h as their first line will
>> be fixed up.  If that proves acceptable, I'll submit one or more
>> further series to move the various includes currently common to
>> defs.h and server.h into common-defs.h, and finally something to
>> switch common/target/nat files over to common-defs.h.
>
> Sounds good to me.  I've distilled this into the wiki:
>
>   https://sourceware.org/gdb/wiki/Common#Header_files_in_common_code_.28defs.h_vs_server.h.2C_etc..29
>
> Please do feel free to edit it / improve it.
>
> (obviously that can evolve if the plan is objected to and changes.)

fyi,
There is also:
https://sourceware.org/gdb/wiki/Internals%20GDB-C-Coding-Standards

which will need updating, e.g., to reference what to do for common files.


  parent reply	other threads:[~2014-07-29 16:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 12:51 [PATCH 0/3 v4] Common code cleanups (part 1) Gary Benson
2014-07-24 12:51 ` [PATCH 1/3 v4] Introduce common/errors.h Gary Benson
2014-07-24 13:24   ` Pedro Alves
2014-07-24 18:03     ` Doug Evans
2014-07-25  8:51       ` Gary Benson
2014-07-25 10:32         ` Pedro Alves
2014-07-25 11:38           ` Gary Benson
2014-07-25 12:13             ` Pedro Alves
2014-07-25 13:34               ` Gary Benson
2014-07-29 16:44               ` Doug Evans [this message]
2014-07-29 17:45                 ` Pedro Alves
2014-07-30  9:43                   ` Gary Benson
2014-07-25 10:19       ` Pedro Alves
2014-07-24 17:52   ` Doug Evans
2014-07-24 22:39     ` Doug Evans
2014-07-25  9:34     ` Gary Benson
2014-07-28 20:16       ` Doug Evans
2014-07-24 12:51 ` [PATCH 2/3 v4] Remove some GDBSERVER checks from linux-ptrace Gary Benson
2014-07-24 13:25   ` Pedro Alves
2014-07-24 14:09     ` Tom Tromey
2014-07-24 14:17       ` Pedro Alves
2014-07-24 14:13     ` [PATCH 2/3 v5] " Gary Benson
2014-07-24 14:25       ` Pedro Alves
2014-07-24 15:05         ` Gary Benson
2014-07-24 13:08 ` [PATCH 3/3 v4] Make gdbserver CORE_ADDR unsigned Gary Benson
2014-07-24 13:36   ` Pedro Alves
2014-07-24 14:07     ` Gary Benson

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=CADPb22Rrkahzsj388P22Tsj3xdVDhrBBJVSCJNVJO0xBGGRPkQ@mail.gmail.com \
    --to=dje@google.com \
    --cc=gbenson@redhat.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