Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@wdc.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb@sourceware.org
Subject: gdbserver/ considered a part of binutils?
Date: Wed, 19 Feb 2020 02:09:00 -0000	[thread overview]
Message-ID: <alpine.LFD.2.21.2002190157580.18621@redsun52.ssa.fujisawa.hgst.com> (raw)

Hi Tom,

 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.

 Since you have been the person working on this tree restructuring can you 
please figure out what has to be done to get this fixed?

  Maciej


             reply	other threads:[~2020-02-19  2:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19  2:09 Maciej W. Rozycki [this message]
2020-02-19  2:38 ` Joel Brobecker
2020-02-19  3:02   ` Maciej W. Rozycki
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.2002190157580.18621@redsun52.ssa.fujisawa.hgst.com \
    --to=macro@wdc.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