From: Benny Halevy <bhalevy@panasas.com>
To: NFS list <linux-nfs@vger.kernel.org>
Subject: Re: linux-pnfs-cthon git tree
Date: Mon, 21 Feb 2011 14:46:48 -0800 [thread overview]
Message-ID: <4D62EB58.7000600@panasas.com> (raw)
In-Reply-To: <4D62EA13.1000809@panasas.com>
On 2011-02-21 14:41, Benny Halevy wrote:
> I've set up a git tree for Connectathon to hold up the fixes we're testing
> here temporarily. I'll update the main tree when we're done so not to cause
> unnecessary churn.
Oops, here's the tree's url:
git://linux-nfs.org/~bhalevy/linux-pnfs-cthon.git
or
ssh://linux-nfs.org/~bhalevy/exports/linux-pnfs-cthon.git
if you don't have git access (and have ssh access to linux-nfs.org).
If you need local access on the cthon network
the latest tree is also available on
git://10.41.21.1/linux-pnfs.git
However, as it's stored on my laptop it might be unavailable
intermittently. Please coordinate with me when you're pulling it
to make sure it stays up.
Bennny
>
> The following branches have been posted up:
>
> pnfs-all-2.6.37
> pnfs-all-latest # based on v2.6.38-rc5
> pnfs-submit-wave3 # based on v2.6.38-rc5 .. Andy's wave3-rev11 .. Fred's 2 SQUASHMEs
> pnfs-submit-wave4 # based on pnfs-submit-wave3 and Fred's wave4 patches
>
> The -all branches include the fixes for layout recall that I've posted on the mailing list.
>
> Benny
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-02-21 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 22:41 linux-pnfs-cthon git tree Benny Halevy
2011-02-21 22:46 ` Benny Halevy [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=4D62EB58.7000600@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).