From: Chris Mason <chris.mason@oracle.com>
To: Steven Pratt <slpratt@austin.ibm.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: 2.6.31 kernel
Date: Tue, 1 Sep 2009 11:05:48 -0400 [thread overview]
Message-ID: <20090901150548.GA5491@think> (raw)
In-Reply-To: <4A9D2C48.9040002@austin.ibm.com>
On Tue, Sep 01, 2009 at 09:14:32AM -0500, Steven Pratt wrote:
> Chris, are you planning to rebase the full git trees on 2.6.31 any
> time soon?
I was planning on doing it when 2.6.31 came out.
-chris
prev parent reply other threads:[~2009-09-01 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 14:14 2.6.31 kernel Steven Pratt
2009-09-01 15:05 ` Chris Mason [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=20090901150548.GA5491@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=slpratt@austin.ibm.com \
/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