From: Tyler Hicks <tyhicks@canonical.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: fate of the ecryptfs tree
Date: Fri, 1 Jun 2012 16:41:55 -0700 [thread overview]
Message-ID: <20120601234154.GB6340@boyd> (raw)
In-Reply-To: <20120531144115.0f35af0a8a5d79b73b0ecbe6@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
On 2012-05-31 14:41:15, Stephen Rothwell wrote:
> Hi Tyler,
>
> I am just wondering about the fate of the ecryptfs tree. The most recent
> commit to that tree is dated Feb 11 and seems to have been included in
> Linus' tree as a different commit.
My next branch has become stale. Sorry about that! I haven't been doing
much development on the kernel side in the last couple months. That will
soon change, as I have a few bug fixes in the works and I know of a
contribution or two that should surface shortly.
In the meantime, I've just pushed the HEAD of Linus' tree to my next
branch to clean things up.
Tyler
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-01 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 4:41 linux-next: fate of the ecryptfs tree Stephen Rothwell
2012-06-01 23:41 ` Tyler Hicks [this message]
2012-06-02 3:37 ` 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=20120601234154.GB6340@boyd \
--to=tyhicks@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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