Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: eliz@gnu.org, jimb@red-bean.com, sje@cup.hp.com,
	        gdb-patches@sourceware.org
Subject: Re: [PATCH] Remove gdb/nlm subdirectory
Date: Sat, 25 Mar 2006 00:04:00 -0000	[thread overview]
Message-ID: <200603242304.k2ON4iW5014084@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060324144727.GA15703@nevyn.them.org> (message from Daniel 	Jacobowitz on Fri, 24 Mar 2006 09:47:27 -0500)

> Date: Fri, 24 Mar 2006 09:47:27 -0500
> From: Daniel Jacobowitz <drow@false.org>
> 
> On Fri, Mar 24, 2006 at 11:46:20AM +0200, Eli Zaretskii wrote:
> > > Date: Thu, 23 Mar 2006 23:30:08 -0500
> > > From: Daniel Jacobowitz <drow@false.org>
> > > Cc: sje@cup.hp.com, gdb-patches@sourceware.org
> > > 
> > > 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.
> > 
> > Do we have good reasons to believe the nlm stuff is not used, or
> > cannot be built with a reasonable amount of effort?  If so, I see no
> > reason to have the staging period.
> 
> Well, in all the time I've been working on GDB, I've never seen a user
> question about Netware, a GNATS PR about Netware, or a developer commit
> tested on Netware.  To build it you need a Netware-provided SDK; I
> don't know if those are still obtainable.

I believe the last time we proposed this some guy from Novell stepped
up and said he'd like to keep the code.  This must have been around
the time Novell acquired SuSE.  But I never heard from this guy again.

> > Otherwise, let's leave this for the next release.
> 
> I'm fine with that if you'd prefer.  I think we can ignore its old
> configure file for now, then, instead of worrying about upgrading it to
> 2.5x (which started this discussion).

We have no way of checking whether this code still works.  Let's get
rid of it.  If someone complains, he/she can get it out of the attic
and we can add it back if said person converts the configure fragment
to autoconf 2.5x.

Mark


  parent reply	other threads:[~2006-03-24 23:08 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 [this message]
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=200603242304.k2ON4iW5014084@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=drow@false.org \
    --cc=eliz@gnu.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