From: Stephen Rothwell <sfr@ozlabs.org>
To: ppc64-dev <linuxppc64-dev@ozlabs.org>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Posting delays
Date: Tue, 11 Oct 2005 10:53:37 +1000 [thread overview]
Message-ID: <20051011105337.6cda121e.sfr@ozlabs.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
Hi all,
Just a note to let you all know that I have changed the list manager
configuration so that posts from email addresses that are not subscribed
to the list will be held until looked at by one of the admins. This may
cause some delay in peoples postings, sorry. If people are happy with
some (hopefully short) delay, then nothing needs to change - whenever what
looks like a reasonable post is held, I am adding the senders address to
those whom will not be held again.
--
Cheers,
Stephen Rothwell sfr@ozlabs.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2005-10-11 0:53 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=20051011105337.6cda121e.sfr@ozlabs.org \
--to=sfr@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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).