From: Jim Kingdon <kingdon@panix.com>
To: cgf@cygnus.com
Cc: overseers@sourceware.cygnus.com
Subject: Re: [Marco.Craveiro@solvay.com: [postmaster@sourceware] FW: failure notice]
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <200007061544.LAA06602@panix6.panix.com> (raw)
In-Reply-To: <20000706101742.B20254@cygnus.com>
> i've posted to libstdc++ before using the address
> <libstdc++@sourceware.cygnus.com>; for some reason it is now bouncing (see
Oops, my bad.
The check-for-listname script takes a regular expression as an
argument, not a fixed string. I've fixed the invocation in
/qmail/lists-sourceware/libstdc++/editor
Thanks for passing this along, Chris.
WARNING: multiple messages have this Message-ID
From: Jim Kingdon <kingdon@panix.com>
To: cgf@cygnus.com
Cc: overseers@sourceware.cygnus.com
Subject: Re: [Marco.Craveiro@solvay.com: [postmaster@sourceware] FW: failure notice]
Date: Thu, 06 Jul 2000 08:45:00 -0000 [thread overview]
Message-ID: <200007061544.LAA06602@panix6.panix.com> (raw)
Message-ID: <20000706084500.hzFIA8owgF0MZnwr6YPZ5qrKPORBTN_p9Vf6nGfSys4@z> (raw)
In-Reply-To: <20000706101742.B20254@cygnus.com>
> i've posted to libstdc++ before using the address
> <libstdc++@sourceware.cygnus.com>; for some reason it is now bouncing (see
Oops, my bad.
The check-for-listname script takes a regular expression as an
argument, not a fixed string. I've fixed the invocation in
/qmail/lists-sourceware/libstdc++/editor
Thanks for passing this along, Chris.
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Chris Faylor
2000-07-06 7:17 ` Chris Faylor
2000-12-30 6:08 ` Jim Kingdon [this message]
2000-07-06 8:45 ` Jim Kingdon
2000-12-30 6:08 ` Chris Faylor
2000-07-06 10:31 ` Chris Faylor
2000-12-30 6:08 ` Benjamin Kosnik
2000-07-06 9:00 ` Benjamin Kosnik
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=200007061544.LAA06602@panix6.panix.com \
--to=kingdon@panix.com \
--cc=cgf@cygnus.com \
--cc=overseers@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).