From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Don't enable gdbtk in testsuite
Date: Fri, 05 Dec 2014 10:05:00 -0000 [thread overview]
Message-ID: <20141205100535.GG7899@adacore.com> (raw)
In-Reply-To: <548180B5.4060003@redhat.com>
> Personally, I wouldn't be adverse to importing gdbtk into the official
> gdb repo. I don't see how that could hurt -- we tend to worry
> about insight anyway when we touch code that might affect it, like
> most the deprecated_foo hooks.
FWIW - I was hoping insight would be dead by now, but if people
still use it and make updates, then I wouldn't be opposed either.
The one thing to be careful of, I think, is handling of their
commits. Probably just a third email list for insight-specific
files?
--
Joel
next prev parent reply other threads:[~2014-12-05 10:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 8:11 Yao Qi
2014-11-30 15:23 ` Joel Brobecker
2014-12-01 6:15 ` Yao Qi
2014-12-04 17:07 ` Pedro Alves
2014-12-05 6:55 ` Yao Qi
2014-12-05 9:54 ` Pedro Alves
2014-12-05 10:05 ` Joel Brobecker [this message]
2014-12-05 12:04 ` Yao Qi
2014-12-05 11:27 Roland Schwingel
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=20141205100535.GG7899@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=yao@codesourcery.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