From: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
To: linuxppc-dev@lists.linuxppc.org
Subject: Is the list working today?
Date: Mon, 16 Oct 2000 13:39:49 -0400 [thread overview]
Message-ID: <200010161739.MAA15639@lists.linuxppc.org> (raw)
Hi,
I sent an announcement about the JDK 1.3.0 FCS for PPC Linux just released by Blackdown to both the dev and user mailing lists. I receive the user mailing list in digest form so I can't tell when it was rejected or not, but I do receive the dev mailing list in on-digest and even received some from messages from dev today but no copy of my announcement.
I then checked to make sure I was subscribed at the correct address and according to majordomo for dev I am.
Is the dev mailing list working today?
Did anyone see my new JDK announcement?
If not, could someone please check the majordomo logs to see why my mail was rejected (it would be nice to get back a rejected notice). Or are things just backed up and something will actually come through today?
Thanks,
Kevin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-10-16 17:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200010161739.MAA15639@lists.linuxppc.org \
--to=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.org \
/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 NNTP newsgroup(s).