public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* linux-next: fate of the ecryptfs tree
@ 2012-05-31  4:41 Stephen Rothwell
  2012-06-01 23:41 ` Tyler Hicks
  0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2012-05-31  4:41 UTC (permalink / raw)
  To: Tyler Hicks; +Cc: linux-next, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 268 bytes --]

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.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: linux-next: fate of the ecryptfs tree
  2012-05-31  4:41 linux-next: fate of the ecryptfs tree Stephen Rothwell
@ 2012-06-01 23:41 ` Tyler Hicks
  2012-06-02  3:37   ` Stephen Rothwell
  0 siblings, 1 reply; 3+ messages in thread
From: Tyler Hicks @ 2012-06-01 23:41 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: linux-next, linux-kernel

[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: linux-next: fate of the ecryptfs tree
  2012-06-01 23:41 ` Tyler Hicks
@ 2012-06-02  3:37   ` Stephen Rothwell
  0 siblings, 0 replies; 3+ messages in thread
From: Stephen Rothwell @ 2012-06-02  3:37 UTC (permalink / raw)
  To: Tyler Hicks; +Cc: linux-next, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

Hi Tyler,

On Fri, 1 Jun 2012 16:41:55 -0700 Tyler Hicks <tyhicks@canonical.com> wrote:
>
> On 2012-05-31 14:41:15, Stephen Rothwell wrote:
> > 
> > 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.

Thanks for that.

> In the meantime, I've just pushed the HEAD of Linus' tree to my next
> branch to clean things up.

Excellent.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-06-02  3:37 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-31  4:41 linux-next: fate of the ecryptfs tree Stephen Rothwell
2012-06-01 23:41 ` Tyler Hicks
2012-06-02  3:37   ` Stephen Rothwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox