public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: pNFS Mailing List <pnfs@linux-nfs.org>, nfsv4 <nfsv4@linux-nfs.org>
Cc: "J. Bruce Fields" <bfields@citi.umich.edu>,
	NFS list <linux-nfs@vger.kernel.org>
Subject: Merge {nfsv4,pnfs}@linux-nfs.org with linux-nfs@vger.kernel.org?
Date: Tue, 27 Apr 2010 21:14:58 +0300	[thread overview]
Message-ID: <4BD729A2.3000805@panasas.com> (raw)

Forwarding to the linux-nfs.org lists.

On Apr. 27, 2010, 21:10 +0300, "J. Bruce Fields" <bfields@citi.umich.edu> wrote:

On Tue, Apr 27, 2010 at 07:44:51PM +0300, Benny Halevy wrote:
> On Apr. 27, 2010, 19:34 +0300, "J. Bruce Fields" <bfields@citi.umich.edu> wrote:
> > The main lists we've been using are:
> > 
> > 	linux-nfs@vger.kernel.org
> > 	    nfsv4@linux-nfs.org
> > 	     pnfs@linux-nfs.org
> > 
> > This seems to be confusing.  We've talked before about transitioning
> > away from one (probably nfsv4@linux-nfs.org).  Maybe now's the time to
> > start.
> 
> I'm all for it.
> Maybe it's time to fold the pnfs list into linux-nfs too.

So, looking back at what we did for the sourceforge list:

	- We added something to the footer saying the list is
	  deprecated.  (But if we wanted to be more obnoxious, we could
	  add it to the top of each message.)

	- We subscribed the new list (linux-nfs@vger.kernel.org) to the
	  old list, I guess so newbie bug reports sent to the old list
	  wouldn't get lost.

Anyone want to object to starting that process for nfsv4@linux-nfs.org?
What about pnfs@linux-nfs.org?

--b.

             reply	other threads:[~2010-04-27 18:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27 18:14 Benny Halevy [this message]
2010-04-27 18:33 ` Merge {nfsv4,pnfs}@linux-nfs.org with linux-nfs@vger.kernel.org? Trond Myklebust
     [not found]   ` <1272393184.3067.27.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-04-27 18:36     ` Trond Myklebust
2010-04-28 15:02       ` J. Bruce Fields
2010-04-28 16:13         ` J. Bruce Fields

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=4BD729A2.3000805@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=bfields@citi.umich.edu \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@linux-nfs.org \
    --cc=pnfs@linux-nfs.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