From: "Maciej W. Rozycki" <macro@wdc.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tom@tromey.com>, gdb@sourceware.org
Subject: Re: gdbserver/ considered a part of binutils?
Date: Wed, 19 Feb 2020 03:02:00 -0000 [thread overview]
Message-ID: <alpine.LFD.2.21.2002190248320.18621@redsun52.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <20200219023801.GY10825@adacore.com>
On Wed, 19 Feb 2020, Joel Brobecker wrote:
> > It seems like something has to be done with Git hook scriptery to make it
> > consider gdbserver/ a part of GDB rather than binutils; gdbsupport/ might
> > be similarly affected. My recent commit spanning gdb/ and gdbserver/ has
> > triggered an additional message (beyond one to <gdb-cvs@sourceware.org>)
> > posted to <bfd-cvs@sourceware.org>, which shouldn't have happened for such
> > a commit.
>
> I should be the same message with two recipients, but that's indeed
> a good point. This is something to remember when moving code to
> the toplevel dir.
Yes, it's a single original message, but if you're subscribed to both
mailing lists then you receive two copies of the message as I did.
> I've modified the script we use to determine which mailing-list to hit,
> and marked gdbserver/ and gdbsupport/ as being GDB-only. I did a quick
> pass over the current directories at toplevel, and didn't see anything
> else. But if there are other directories not created yet that we are
> planning on adding, please let me know, and I will take care of it too.
Great, thanks, also for your sharp-sightedness!
Maciej
next prev parent reply other threads:[~2020-02-19 3:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 2:09 Maciej W. Rozycki
2020-02-19 2:38 ` Joel Brobecker
2020-02-19 3:02 ` Maciej W. Rozycki [this message]
2020-02-19 22:28 ` Tom Tromey
2020-02-20 2:50 ` Joel Brobecker
2020-02-20 16:45 ` Tom Tromey
2020-02-21 3:42 ` 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=alpine.LFD.2.21.2002190248320.18621@redsun52.ssa.fujisawa.hgst.com \
--to=macro@wdc.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).