From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: introduce common.m4
Date: Mon, 22 Jul 2013 17:49:00 -0000 [thread overview]
Message-ID: <87vc425vue.fsf@fleche.redhat.com> (raw)
In-Reply-To: <517ACB2C.2030006@redhat.com> (Pedro Alves's message of "Fri, 26 Apr 2013 19:45:00 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
[ old-ish thread... ]
Pedro> IMO, it's a little better if each subdirectory treats the
Pedro> others more as black boxes. gdb/ relying on common/'s
Pedro> HAVE_FOO checks feels like gdb/ relying on common/'s
Pedro> implementation details to me. But I don't want to impose.
Yeah, I agree. When I refresh this patch I will do it this way.
Lately I have been thinking that common and gdbserver should be
top-level directories (after renaming "common" something more suitable).
This would let us use libiberty in gdbserver while still preserving, I
think, the ability to build gdbserver separately. Also it would let us
treat "common" as a true library, not as the odd beast it is today.
Perhaps gnulib would also have to be pushed up.
Tom
next prev parent reply other threads:[~2013-07-22 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 20:51 Tom Tromey
2013-04-24 23:16 ` Pedro Alves
2013-04-25 1:47 ` Tom Tromey
2013-04-25 2:45 ` Pedro Alves
2013-04-25 5:48 ` Tom Tromey
2013-04-26 21:01 ` Pedro Alves
2013-07-22 17:49 ` Tom Tromey [this message]
2013-07-26 15:34 ` Pedro Alves
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=87vc425vue.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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