From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@red-bean.com>
Cc: sje@cup.hp.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Remove gdb/nlm subdirectory
Date: Fri, 24 Mar 2006 09:10:00 -0000 [thread overview]
Message-ID: <20060324043008.GA5092@nevyn.them.org> (raw)
In-Reply-To: <8f2776cb0603232024u163c75edm20eb01ff1d476d18@mail.gmail.com>
On Thu, Mar 23, 2006 at 08:24:54PM -0800, Jim Blandy wrote:
> In the past we've generally marked something as outgoing for a
> release, and then actually removed it in the next, or something
> roughly like that, to give people some warning in case someone wants
> to step up and maintain the code. On the other hand, I think GDB's
> policies have accumulated a lot of dead weight over the last few
> years; some existing practices are more trouble than they're worth, in
> my opinion.
>
> So I'm not sure it's deathly important to do a staged phase-out of the
> nlm directory. But I'd like to see some other maintainers' opinions
> on it, so that we're making a deliberate choice as a group about how
> to handle these cases.
For things that folks still might, conceivably, be using in current
versions of GDB, and things that we still reasonably expect to work,
the obsoletion interval makes sense. However, we've recently removed
one piece without that interval (rdi-share), and I've got my eye on two
others right now (KOD, which there was already agreement to remove;
just need to do it), and remote-rdp.c. I think that's perfectly
appropriate.
I wouldn't mind pruning some of the other remote targets while we're
here, either - e.g. remote-mips.c.
I'm in favor of removing gdb/nlm/, but let's take another couple of
days to see if anyone disagrees.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-24 4:30 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 [this message]
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
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=20060324043008.GA5092@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@red-bean.com \
--cc=sje@cup.hp.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