From: Andrew Cagney <cagney@gnu.org>
To: David Carlton <david.carlton@sun.com>, Jim Blandy <jimb@redhat.com>
Cc: gdb@sources.redhat.com, gdb-discuss@gnu.org
Subject: Re: [Gdb-discuss] Should we close down gdb-discuss@gnu.org?
Date: Thu, 24 Jun 2004 18:19:00 -0000 [thread overview]
Message-ID: <40DB1B2E.1080104@gnu.org> (raw)
In-Reply-To: <yf2n02w8pjq.fsf@kealia.sfbay.sun.com>
> .. but I would lean towards leaving the
> list in place until that happens.
Yes.
Jim,
I suspect this is really a marketing problem. Can I suggest approaching
the posters and just ask them what information they relied on when
identifying that list?
We not so recently had a similar problem with PRMS vs bug-gdb . It
turned out that users were dilligently (and obviously correctly)
following instructions in one of the README files, oops! Once that was
fixed the problem largely went away!
Andrew
PS: The mail archives appear to be broken :-(
next prev parent reply other threads:[~2004-06-24 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 22:12 Jim Blandy
2004-06-21 23:22 ` [Gdb-discuss] " David Carlton
2004-06-24 18:19 ` Andrew Cagney [this message]
2004-06-28 20:43 ` Jim Blandy
2004-06-29 0:21 ` Michael Snyder
2004-07-06 17:29 ` Jim Blandy
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=40DB1B2E.1080104@gnu.org \
--to=cagney@gnu.org \
--cc=david.carlton@sun.com \
--cc=gdb-discuss@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.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