From: "H. J. Lu" <hjl@lucon.org>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: nfs@lists.sourceforge.net
Subject: Re: ADMINSTRIVIA - Intent to open nfs@lists.sourceforge.net to non-subscribers.
Date: Thu, 22 Sep 2005 01:56:19 -0700 [thread overview]
Message-ID: <20050922085619.GA31016@lucon.org> (raw)
In-Reply-To: <17201.34296.859729.69509@cse.unsw.edu.au>
On Wed, Sep 21, 2005 at 06:10:32PM +0200, Neil Brown wrote:
>
> Greetings.
>
> It is generally accepted in the linux-kernel community that mailing
> lists for discussion problems with parts of the kernel should not be
> subscriber-only. This is (in part) because subscriber-only lists
> increase the barrier to submitting useful problem reports, and we
> want to get useful problem reports.
>
> Hence, I intend to switch nfs@lists.sourceforge.net to accept mail
> from non-subscribers.
>
> If you have a violent objection to this, please write now.
> I don't believe a fear of 'SPAM' is a reasonable objection as there
> are plenty of tools available that reduce SPAM substantially.
>
I have no objection.
H.J.
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-09-22 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 16:10 ADMINSTRIVIA - Intent to open nfs@lists.sourceforge.net to non-subscribers Neil Brown
2005-09-21 16:16 ` Brian J. Murrell
2005-09-22 8:56 ` H. J. Lu [this message]
2005-10-06 13:41 ` J. Bruce Fields
2005-10-06 22:46 ` Neil Brown
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=20050922085619.GA31016@lucon.org \
--to=hjl@lucon.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.