public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-fsdevel@vger•kernel.org,
	Linux Containers <containers@lists•linux-foundation.org>
Subject: Can you add the binfmt_misc tree to linux-next?
Date: Mon, 27 Jun 2016 09:16:38 -0700	[thread overview]
Message-ID: <1467044198.2264.19.camel@HansenPartnership.com> (raw)

Since I'd effectively become binfmt_misc maintainer when these patches
get merged on the last person to touch it owns it principle, it makes
sense to begin now more formally.  The tree is at

git://git.kernel.org/pub/scm/linux/kernel/git/jejb/binfmt_misc.git for-next

It currently contains four patches adding the container emulation
infrastructure from the persistent-handlers branch.

Thanks,

James


             reply	other threads:[~2016-06-27 16:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 16:16 James Bottomley [this message]
2016-06-27 23:29 ` Can you add the binfmt_misc tree to linux-next? Stephen Rothwell
2016-06-27 23:57   ` James Bottomley

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=1467044198.2264.19.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership$(echo .)com \
    --cc=containers@lists$(echo .)linux-foundation.org \
    --cc=linux-fsdevel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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