From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Remove gdb/nlm subdirectory
Date: Tue, 28 Mar 2006 22:18:00 -0000 [thread overview]
Message-ID: <20060328212328.GA10724@nevyn.them.org> (raw)
In-Reply-To: <20060328211848.GB10392@nevyn.them.org>
On Tue, Mar 28, 2006 at 04:18:48PM -0500, Daniel Jacobowitz wrote:
> On Sat, Mar 25, 2006 at 10:16:09AM +0200, Eli Zaretskii wrote:
> > I interpreted Daniel's message as something like ``I'm not sure, I
> > just know we never heard any problem or patch''. Which to me doesn't
> > sound as firm reasons, just as lack of any information.
>
> That's right. But, Ian has now provided evidence that it wouldn't
> build without hacking the GDB sources since before GDB 6.0; is that
> enough to remove it directly, in your opinion?
[Oops! Sorry for moving this to gdb, I fat-fingered it. Moving it
back now!]
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-28 21:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 3:27 Steve Ellcey
2006-03-24 8:31 ` Jim Blandy
2006-03-24 9:10 ` Daniel Jacobowitz
2006-03-24 20:21 ` Eli Zaretskii
2006-03-24 20:23 ` Daniel Jacobowitz
2006-03-24 20:30 ` Jim Blandy
2006-03-25 16:23 ` Eli Zaretskii
2006-03-25 0:04 ` Mark Kettenis
2006-03-25 6:57 ` Jim Blandy
2006-03-25 13:05 ` Eli Zaretskii
[not found] ` <20060328211848.GB10392@nevyn.them.org>
2006-03-28 22:18 ` Daniel Jacobowitz [this message]
2006-03-29 15:58 ` Eli Zaretskii
2006-03-27 13:25 ` Ian Lance Taylor
2006-03-27 14:52 ` Daniel Jacobowitz
2006-03-27 23:59 ` Ian Lance Taylor
2006-03-24 17:29 ` Eli Zaretskii
2006-03-29 23:40 ` Daniel Jacobowitz
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=20060328212328.GA10724@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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