From: "J. Bruce Fields" <bfields@fieldses.org>
To: Weston Andros Adamson <dros@netapp.com>
Cc: Jim Rees <rees@umich.edu>, Ben Greear <greearb@candelatech.com>,
linux-nfs@vger.kernel.org
Subject: Re: What is proper kernel tree to develop against?
Date: Wed, 8 Jun 2011 16:13:14 -0400 [thread overview]
Message-ID: <20110608201314.GC6752@fieldses.org> (raw)
In-Reply-To: <6598B49E-A6F0-4D7B-AC82-A675CF69E9C8@netapp.com>
On Wed, Jun 08, 2011 at 03:49:38PM -0400, Weston Andros Adamson wrote:
>
> On Jun 8, 2011, at 3:03 PM, J. Bruce Fields wrote:
>
> > On Wed, Jun 08, 2011 at 02:52:19PM -0400, Jim Rees wrote:
> >> Ben Greear wrote:
> >>
> >> What kernel tree should I use to develop NFS & RPC patches
> >> for possible upstream acceptance?
> >>
> >> I think for the stuff you're doing it would just be the upstream git tree at
> >> kernel.org. Note that nfs-utils is separate.
> >>
> >> Has anyone pointed you to the wiki? I think it answers many of these
> >> questions, although it seems heavily slanted towards pnfs.
> >>
> >> http://wiki.linux-nfs.org/wiki/index.php/Main_Page
> >
> > It would be nice to reorganize the wiki, especially that top page.
> >
> > I'd kind of like linux-nfs.org to just point to some page on the wiki
> > some day.
>
> I've actually signed up to revamp linux-nfs.org. I'll begin work on that very soon (after bakeathon and my vacation).
OK, good!
--b.
prev parent reply other threads:[~2011-06-08 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 18:41 What is proper kernel tree to develop against? Ben Greear
2011-06-08 18:52 ` Jim Rees
2011-06-08 19:03 ` J. Bruce Fields
2011-06-08 19:49 ` Weston Andros Adamson
2011-06-08 20:13 ` J. Bruce Fields [this message]
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=20110608201314.GC6752@fieldses.org \
--to=bfields@fieldses.org \
--cc=dros@netapp.com \
--cc=greearb@candelatech.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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.