Linux NFS development
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: nfs@lists.sourceforge.net
Subject: [ADMIN] Please transfer your subscription from nfs@lists.sourceforge.net to linux-nfs@vger.kernel.org
Date: Fri, 16 Nov 2007 16:03:50 +1100	[thread overview]
Message-ID: <18237.9398.845711.226261@notabene.brown> (raw)


Greetings,

 due to a variety of dissatisfactions with the mailing list service at
 sourceforge (spam problems, inconvenient auto-unsubscription) the
 list 
    nfs@lists.sourceforge.net
 is being discontinued.
 The list linux-nfs@vger.kernel.org has been created to replace it.

 What you should do:

  1/ subscribe to linux-nfs@vger.kernel.org

    See linux-nfs@vger.kernel.org  for details

  2/ unsubscribe from nfs@lists.sourceforge.net

      You can do this from this page:

        https://lists.sourceforge.net/lists/listinfo/nfs

  All mail to nfs@lists.sourceforge.net will before forwarded to
  linux-nfs for at least the rest of this year (but probably not much
  beyond that).  So you won't miss anything.

  I have asked for MARC and GMANE to subscribe to the new list.  If
  you have another favourite mail archive, you might like to ask them
  to subscribe to the new list too.


 Further subscription to nfs@lists.sourceforge.net will not be
 accepted.

 I suspect that the only dissatisfaction that people might have with
 the vger list is that you won't get '[NFS]' in the subject.  Most
 mail readers should be able to filter on the 'to' header so that you
 don't need to visually filter on the 'subject' header.  I'm sure that
 if it is really an issue, someone will post a clever procmail rule
 which puts the '[NFS]' back :-)

I hope this will not inconvenience anyone.

In case any one is interested, there are currently 638 addresses
subscribed to nfs@lists.sourceforge.net.  Let's see if we can make it
below 300 by December :-)
Similarly there are currently 21 subscriptions to linux-nfs. Can we
make it 100 by next week?

NeilBrown

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
    http://vger.kernel.org/vger-lists.html#linux-nfs

             reply	other threads:[~2007-11-16  5:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16  5:03 Neil Brown [this message]
2007-11-16  6:29 ` [ADMIN] Please transfer your subscription from nfs@lists.sourceforge.net to linux-nfs@vger.kernel.org Neil Brown
2007-11-16  9:36   ` Neil Brown
2007-11-16 17:33 ` Steinar H. Gunderson
2007-11-17  8:17   ` [ADMIN] Please transfer your subscription from nfs@lists.sourceforge.net to linux-nfs@vger Suresh Jayaraman
2007-11-17 20:52   ` [NFS] [ADMIN] Please transfer your subscription from nfs@lists.sourceforge.net to linux-nfs@vger.kernel.org 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=18237.9398.845711.226261@notabene.brown \
    --to=neilb@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox