From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Stan Shebs <stanshebs@earthlink.net>, gdb-patches@sourceware.org
Subject: Re: RFA: move *-stub.c to stubs/
Date: Mon, 12 Mar 2012 23:15:00 -0000 [thread overview]
Message-ID: <4F5E8384.3000905@redhat.com> (raw)
In-Reply-To: <20120312230434.GQ2853@adacore.com>
On 03/12/2012 11:04 PM, Joel Brobecker wrote:
>> Just now noticing this - do we really want a separate ChangeLog in
>> the subdir? The last time it came up, people seemed to want fewer
>> ChangeLogs, not more.
>
> That's a good point. Any objection to fixing this?
That came in in the context of docs and tests. But in this case, does it really make sense
to have essentially separate programs' logs in gdb's ChangeLog? IMO, it doesn't. IMO, it kind
of follows exactly from putting the files in their own dir. They're separate things, not part
of GDB.
--
Pedro Alves
next prev parent reply other threads:[~2012-03-12 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 16:04 Tristan Gingold
2012-03-05 17:16 ` Pedro Alves
2012-03-05 17:22 ` Joel Brobecker
2012-03-08 14:44 ` Tristan Gingold
2012-03-12 22:30 ` Stan Shebs
2012-03-12 23:04 ` Joel Brobecker
2012-03-12 23:15 ` Pedro Alves [this message]
2012-03-13 0:35 ` Joel Brobecker
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=4F5E8384.3000905@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
/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