From: Benny Halevy <bhalevy@panasas.com>
To: NFS list <linux-nfs@vger.kernel.org>
Subject: pnfs-all-2.6.35-rc2-2010-06-06 is out
Date: Mon, 07 Jun 2010 08:33:36 +0300 [thread overview]
Message-ID: <4C0C84B0.5010900@panasas.com> (raw)
Howdy,
I've rebased the linux pnfs tree onto 2.6.35 with the tip tagged as
pnfs-all-2.6.35-rc2-2010-06-06
Development branches structure remains the same:
master (2.6.345-rc2)
pnfs-submit
pnfs
pnfs-block
pnfsd-files
pnfsd
spnfs
spnfs-block
pnfsd-lexp
pnfs-submit-all
pnfs-all
pnfs-obj-all
pnfs-exofs-all
pnfs-block-all
spnfs-all
spnfs-block-all
pnfs-all-latest
Let's try to get everything we want to test in the upcoming bakeathon into
the tree in a decent shape.
Cumulative diff against mainline can be generated as usual using:
$ git diff v2.6.35-rc2 pnfs-all-2.6.35-rc2-2010-06-06
http://wiki.linux-nfs.org/wiki/index.php/PNFS_Development_Git_tree
has been updated to reflect the latest tags.
Benny
reply other threads:[~2010-06-07 5:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4C0C84B0.5010900@panasas.com \
--to=bhalevy@panasas.com \
--cc=linux-nfs@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.