From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Benny Halevy <bhalevy@panasas.com>
Cc: pNFS Mailing List <pnfs@linux-nfs.org>,
nfsv4 <nfsv4@linux-nfs.org>,
"J. Bruce Fields" <bfields@citi.umich.edu>,
NFS list <linux-nfs@vger.kernel.org>
Subject: Re: Merge {nfsv4,pnfs}@linux-nfs.org with linux-nfs@vger.kernel.org?
Date: Tue, 27 Apr 2010 14:36:57 -0400 [thread overview]
Message-ID: <1272393417.3067.30.camel@localhost.localdomain> (raw)
In-Reply-To: <1272393184.3067.27.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
On Tue, 2010-04-27 at 14:33 -0400, Trond Myklebust wrote:
> > On Apr. 27, 2010, 21:10 +0300, "J. Bruce Fields" <bfields@citi.umich.edu> wrote:
> > 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?
>
> ACK to both...
>
>
Oh... The other thing to do is to turn off moderation. I'm sure that
Bruce and I have better things to do than to act as spam filters on
legacy mailing lists...
next prev parent reply other threads:[~2010-04-27 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 18:14 Merge {nfsv4,pnfs}@linux-nfs.org with linux-nfs@vger.kernel.org? Benny Halevy
2010-04-27 18:33 ` Trond Myklebust
[not found] ` <1272393184.3067.27.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-04-27 18:36 ` Trond Myklebust [this message]
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=1272393417.3067.30.camel@localhost.localdomain \
--to=trond.myklebust@netapp.com \
--cc=bfields@citi.umich.edu \
--cc=bhalevy@panasas.com \
--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 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.