From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: Stan Shebs <stanshebs@earthlink.net>, gdb-patches@sourceware.org
Subject: Re: RFA: move *-stub.c to stubs/
Date: Tue, 13 Mar 2012 00:35:00 -0000 [thread overview]
Message-ID: <20120313003457.GA24422@adacore.com> (raw)
In-Reply-To: <4F5E8384.3000905@redhat.com>
> 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.
Hmm, valid points too. I agree it's better to keep the extra CL, now.
--
Joel
prev parent reply other threads:[~2012-03-13 0:35 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
2012-03-13 0:35 ` Joel Brobecker [this message]
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=20120313003457.GA24422@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--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