From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: question about the common/ subdir (was "Re: Ping: Merge duplicated macros in linux-nat.c and linux-low.c")
Date: Mon, 28 Feb 2011 14:35:00 -0000 [thread overview]
Message-ID: <20110228140639.GG30306@adacore.com> (raw)
In-Reply-To: <4D6B96DC.5090606@codesourcery.com>
> > gdb/
> >
> > * linux-nat.c: Move common macros to ...
> > Include linux-ptrace.h.
> > * common/linux-ptrace.h: ... here. New.
> >
> > gdb/gdbserver/
> >
> > * linux-low.c: Move common macros to linux-ptrace.h.
> > Include linux-ptrace.h.
> > * Makefile.in (linux_ptrace_h): New.
> > (linux-low.o): Depends on linux-ptrace.h.
Speaking of which, what was the latest decision regarding the
way we would handle the sources in common/. I thought that we
were going to delete the configury and Makefile, and treat this
the same way we treat the gnulib/ directory. Was that ever
decided? I personally would like to give this idea a try and
see where it goes, but I'm not enough of an expert to really
predict whether it's going to be better or not. I can look
at producing patches, though.
--
Joel
next prev parent reply other threads:[~2011-02-28 14:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 8:24 [common] Merge duplicated macros in linux-nat.c and linux-low.c Yao Qi
2011-02-18 9:36 ` Jan Kratochvil
2011-02-18 14:54 ` Yao Qi
2011-02-18 15:14 ` Mark Kettenis
2011-02-18 16:14 ` Pedro Alves
2011-02-18 15:24 ` Tom Tromey
2011-02-18 15:46 ` Yao Qi
2011-02-18 15:55 ` Tom Tromey
2011-02-18 15:52 ` Pedro Alves
2011-02-18 17:21 ` Yao Qi
2011-02-20 21:34 ` Yao Qi
2011-02-28 12:38 ` Ping: " Yao Qi
2011-02-28 14:35 ` Joel Brobecker [this message]
2011-02-28 14:54 ` question about the common/ subdir (was "Re: Ping: Merge duplicated macros in linux-nat.c and linux-low.c") Yao Qi
2011-02-28 15:11 ` Pedro Alves
2011-02-28 15:00 ` Pedro Alves
2011-03-11 5:05 ` Ping: Merge duplicated macros in linux-nat.c and linux-low.c Yao Qi
2011-03-29 7:46 ` Yao Qi
2011-04-07 14:06 ` Yao Qi
2011-04-25 17:04 ` [common] " Tom Tromey
2011-04-26 15:39 ` Yao Qi
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=20110228140639.GG30306@adacore.com \
--to=brobecker@adacore.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