From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jimb@red-bean.com
Cc: gdb@sourceware.org, fnasser@redhat.com
Subject: Re: Is the current KOD code useful?
Date: Sat, 21 Jan 2006 10:09:00 -0000 [thread overview]
Message-ID: <200601202233.k0KMX3co000072@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <8f2776cb0601201422r6923451fg92a4b07bc3444fe6@mail.gmail.com> (message from Jim Blandy on Fri, 20 Jan 2006 14:22:37 -0800)
> Date: Fri, 20 Jan 2006 14:22:37 -0800
> From: Jim Blandy <jimb@red-bean.com>
>
> On 1/20/06, Jim Blandy <jimb@red-bean.com> wrote:
> > On 1/20/06, Daniel Jacobowitz <drow@false.org> wrote:
> > > Copying this to Fernando, since I belatedly noticed Fernando's entry
> > > in MAINTAINERS for this today. Oops!
> >
> > Michael Snyder has been working a lot with Cisco of late; he's offered
> > to ask around there to see if people are still using it, for what
> > that's worth.
>
> The word from Cisco is that they're not using KOD these days.
Then I propose that, unless Fernando objects, we remove KOD from gdb.
Mark
prev parent reply other threads:[~2006-01-20 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 20:53 Daniel Jacobowitz
2006-01-20 20:53 ` Daniel Jacobowitz
2006-01-20 22:21 ` Jim Blandy
2006-01-20 22:33 ` Jim Blandy
2006-01-21 10:09 ` Mark Kettenis [this message]
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=200601202233.k0KMX3co000072@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=fnasser@redhat.com \
--cc=gdb@sourceware.org \
--cc=jimb@red-bean.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