This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gdbserver/ considered a part of binutils?
- From: "Maciej W. Rozycki" <macro at wdc dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Tom Tromey <tom at tromey dot com>, gdb at sourceware dot org
- Date: Wed, 19 Feb 2020 03:01:52 +0000 (GMT)
- Subject: Re: gdbserver/ considered a part of binutils?
- Ironport-sdr: PnRF411zEAmiC7DYVhRgVm52W9m27QzmMEQ8eUBsUN1g5j23Bm9VVB+atPV6FYuw6b8JEhsKig 2B7CmyxccOQFJyMUOV42rLHVMkBZ0ZgW793HIFM8UTfY+eiTzwqGhO+JTcn2BOZPgXQ2ShDGAx oAcn+FDUKeVUz3J59jUE93wEy8GL2DMIgSbCv1WDCqf5ditaJLakTtNjFI2NW1u4Fkog4ukLn/ A91pPFjuZF2jeytDeqdjKvDixm0ijj4EP9G8slbxEM6/89QtFmWW2JZw6Y4kE3AzAKnkD1MjFC G3M=
- Ironport-sdr: vmUYQL6ykKPAIhlq1kbcxyrG9xa3luZT3qkobDQk7BvpsJ7HKLeXvOjF5KlLd241SX8GldfHSp 1SnAXS2CKVJJGP7kJCHxxwW5BCpZP9EnUZl7vUsL4vyYIlRY/tHyvXXGlE8SksWdfg4dFRayNI Is9m4ro1chLp6MmcXakkq6AzD+D9Cw+R3cJcEN8YJRkrpdecBDKsJSpqkiYYTV4ChTySlelExL c+M5T3gAoyQmlqv1NxO+KcTE8YxE4WEoB2oLjFOsdTPRNuWTNNLEha2UdAChxQC/LXWNrj504l dEe4A5PQsuaQuD7iDRiNtLAz
- Ironport-sdr: XPNHGPDG9qju7wxv0+/clndMPbWaCCZJYOrY44BuEQbdyE/j242/z/tqBlh90NpkEeIk3Gzffz akxfb9YYcatREQV50CVK/XbCUpLqpVGvSge2RkSo94jFvNyZPCxNFbibcvkmtWd9QPXxSSld0L Lno5hSBQXzXyJIkrq7nJHq9dKPPnGX+REgBs5LiZpi98eJRq/b9rbqtc1AYloNifQ8mDyIykAM sGyn0A+J8B/Og4zeUFcH0pksI9kAvuXuoN3a+wT9W9QlNLkmSO0Ht5nvmFWAcy0yQoFiGBtSOZ NQw=
- References: <alpine.LFD.2.21.2002190157580.18621@redsun52.ssa.fujisawa.hgst.com> <20200219023801.GY10825@adacore.com>
- Wdcironportexception: Internal
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