From: "J. Bruce Fields" <bfields@citi.umich.edu>
To: Benny Halevy <bhalevy@panasas.com>
Cc: linux-nfs@vger.kernel.org, postmaster@vger.kernel.org
Subject: Re: [PATCH 1/2] nfsd4: complete enforcement of 4.1 op ordering
Date: Tue, 27 Apr 2010 12:34:04 -0400 [thread overview]
Message-ID: <20100427163404.GH30729@fieldses.org> (raw)
In-Reply-To: <4BD70F5F.7080409@panasas.com>
On Tue, Apr 27, 2010 at 07:22:55PM +0300, Benny Halevy wrote:
> On Apr. 27, 2010, 19:12 +0300, "J. Bruce Fields" <bfields@citi.umich.edu> wrote:
> > On Tue, Apr 27, 2010 at 06:46:43PM +0300, Benny Halevy wrote:
> >> On Apr. 27, 2010, 18:01 +0300, "J. Bruce Fields" <bfields@citi.umich.edu> wrote:
> >>> On Tue, Apr 27, 2010 at 05:40:53PM +0300, Benny Halevy wrote:
> >>>> Bruce, Oddly enough I didn't receive the patch you're commenting on into
> >>>> my inbox. It already happened before on this list and I've no idea what
> >>>> could have went wrong. (I also have a gmail account subscribed on this list
> >>>> and I can't find it there, even in the spam folder :-/)
> >>>
> >>> Huh. I see it in various archives, so I'll assume the problem's on your
> >>> end.
> >>>
> >>
> >> I see it on the archives too, but since I don't ever erase anything out
> >> of my gmail lists account the fact that it's not there AND not
> >> on my panasas account as well is really suspicious. I wonder if
> >> vger had some sort of outage or glitch that could explain that.
> >
> > For what it's worth I've found postmaster at vger.kernel.org can
> > sometimes help troubleshoot problems.
> >
> > --b.
>
> Oddly enough, it seems like I'm subscribed this list (called "linux-nfsv4"):
> http://marc.info/?l=linux-nfsv4&r=1&b=201004&w=2
> rather than
> http://marc.info/?l=linux-nfs&r=1&b=201004&w=2
>
> Although my subscription messages from majordomo@vger.kernel.org
> say "linux-nfs"
>
> The former is essentially nfsv4@linux-nfs.org, right?
> Maybe I got bounced off of linux-nfs.org for some reason...
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.
(Oh, and there's also an older sourceforge list; I think mail still gets
forwarded from the vger list to there? Or is it the other way around?
May be time to turn that one off completely.)
--b.
next prev parent reply other threads:[~2010-04-27 16:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 14:32 [PATCH 1/2] nfsd4: complete enforcement of 4.1 op ordering J. Bruce Fields
2010-04-22 14:32 ` [PATCH 2/2] nfsd4: implement reclaim_complete J. Bruce Fields
2010-04-22 14:48 ` [PATCH 1/2] nfsd4: complete enforcement of 4.1 op ordering J. Bruce Fields
2010-04-22 15:03 ` J. Bruce Fields
2010-04-23 21:24 ` J. Bruce Fields
2010-04-23 23:13 ` J. Bruce Fields
2010-04-24 0:10 ` J. Bruce Fields
2010-04-27 15:03 ` Benny Halevy
2010-04-27 14:40 ` Benny Halevy
2010-04-27 15:01 ` J. Bruce Fields
2010-04-27 15:44 ` Benny Halevy
2010-04-27 16:36 ` J. Bruce Fields
2010-04-27 15:46 ` Benny Halevy
2010-04-27 16:12 ` J. Bruce Fields
2010-04-27 16:22 ` Benny Halevy
2010-04-27 16:34 ` J. Bruce Fields [this message]
2010-04-27 16:44 ` Benny Halevy
2010-04-27 18:10 ` 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=20100427163404.GH30729@fieldses.org \
--to=bfields@citi.umich.edu \
--cc=bhalevy@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=postmaster@vger.kernel.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.