Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: dje@google.com
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Create utils.h and host-defs.h, move gdb_vecs.h to common.
Date: Wed, 18 Jul 2012 20:25:00 -0000	[thread overview]
Message-ID: <87hat424xe.fsf@fleche.redhat.com> (raw)
In-Reply-To: <yjt2liiimfik.fsf@ruffy2.mtv.corp.google.com> (dje@google.com's	message of "Tue, 17 Jul 2012 11:03:31 -0700")

>>>>> "Doug" == Douglas Evans <dje@google.com> writes:

Doug> It's just a code reorg:
Doug> - creates utils.h and moves (almost) all the utils.c decls there from defs.h.
Doug>   I left QUIT&co in defs.h.
Doug> - moves gdb_vecs.h to common and creates common/gdb_vecs.c.
Doug>   I have a followup patch that uses gdb_vecs.c functions in gdbserver.
Doug> - creates common/host-defs.h, DIRNAME_SEPARATOR is needed by gdb_vecs.c.
Doug> - moves probe_p out of gdb_vecs.h, I think a better place for it is probe.h.

It all seems reasonable to me.

Tom


  parent reply	other threads:[~2012-07-18 20:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 18:23 dje
2012-07-17 18:36 ` dje
2012-07-18 20:25 ` Tom Tromey [this message]
2012-07-18 23:36   ` dje

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=87hat424xe.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=dje@google.com \
    --cc=gdb-patches@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