From: robert.thorpe@antenova.com (Rob Thorpe)
Subject: Re: gnu-emacs-bug@gnu.org
Date: 8 Jun 2004 19:25:59 -0700 [thread overview]
Message-ID: <1a61f7e5.0406081825.2e43afdd@posting.google.com> (raw)
In-Reply-To: dIoxc.57585$mQ4.17773@fe2.texas.rr.com
"David Vanderschel" <DJV4@Austin.RR.com> wrote in message news:<dIoxc.57585$mQ4.17773@fe2.texas.rr.com>...
> "Rob Thorpe" <robert.thorpe@antenova.com> wrote in message
> news:1a61f7e5.0406072138.46141bad@posting.google.com...
> > What has happened to gnu-emacs-bug@gnu.org?
> > It doesn't seem to be working.
>
> Try a different name: http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs
>
> Regards,
> David V.
Thats what I meant, when I send mails to bug-gnu-emacs@gnu.org they bounce.
prev parent reply other threads:[~2004-06-09 2:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1a61f7e5.0406072138.46141bad@posting.google.com>
2004-06-08 19:46 ` gnu-emacs-bug@gnu.org David Vanderschel
2004-06-09 2:25 ` Rob Thorpe [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1a61f7e5.0406081825.2e43afdd@posting.google.com \
--to=robert.thorpe@antenova.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).