public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: insight@sourceware.cygnus.com
Subject: New mailing list?
Date: Wed, 31 May 2000 07:47:00 -0000	[thread overview]
Message-ID: <3935260E.95B6EE0E@cygnus.com> (raw)

I would like to propose the creation of the 

    insight-gui@sourceware.cygnus.com

mailing list and the aliasing of  "insight@sourceware.cygnus.com" to
"gdb@sourceware.cygnus.com".

It seems quite obvious right now that people who use gdb from the GUI
call it Insight and send debugger (GUI or non-GUI) messages to the
insight list.

Of course we may get the reverse: people who have GUI related questions
having their messages in the gdb list.  But this is less inconvenient
because:

1) There are less of such cases than the reverse situation.

2) Sometimes the problem is indeed related to the gdb core and not the GUI.

3) Everyone on the insight list is also in the gdb one (the reverse not
   being necessarily true.

Based on 3 we have also the option of having a single list (although I don't
personally like this option, as it will make my life more difficult and will
scare off some people I would never want to see signing off the list because
of the volume).

We can also rename  the "insight" list to "insight-gui" list without creating
the redirection of "insight" to "gdb" (i.e., no more "insight" list).  This 
may be the best option as it makes clear the distinction.

Suggestions are welcome.

Regards to all.

-- 
Fernando Nasser
Red Hat - Toronto                       E-Mail:  fnasser@cygnus.com

             reply	other threads:[~2000-05-31  7:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-31  7:47 Fernando Nasser [this message]
     [not found] <39352941.7304281E@cygnus.com>
     [not found] ` <393F56FD.12B632A0@cygnus.com>
2000-06-08  9:34   ` Fernando Nasser

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=3935260E.95B6EE0E@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=insight@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).