From: Joel Becker <jlbec@evilplan.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: ocfs2-devel@oss.oracle.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Temporary ocfs2 tree location
Date: Tue, 13 Sep 2011 12:18:34 -0700 [thread overview]
Message-ID: <20110913191833.GA5961@noexit.corp.google.com> (raw)
Stephen,
While kernel.org is down, please pull into -next from:
git://oss.oracle.com/git/jlbec/linux-2.6.git linux-next
This should be the same exact branch I had in my kernel.org tree before
it went down (c849cc2a8a30f3fdc05636f44d4ddbbc4719076b).
For provenance, this is the same tree I used to use before I had
a kernel.org account.
Joel
--
Life's Little Instruction Book #20
"Be forgiving of yourself and others."
http://www.jlbec.org/
jlbec@evilplan.org
next reply other threads:[~2011-09-13 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 19:18 Joel Becker [this message]
2011-09-14 0:26 ` Temporary ocfs2 tree location Stephen Rothwell
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=20110913191833.GA5961@noexit.corp.google.com \
--to=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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).