Linux Container Development
 help / color / mirror / Atom feed
From: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Cc: Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: Feeding containers patches into linux-next
Date: Tue, 15 Jul 2008 10:55:16 -0700	[thread overview]
Message-ID: <1216144516.9459.7.camel@nimitz> (raw)
In-Reply-To: <m1d4lff355.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>

On Tue, 2008-07-15 at 10:50 -0700, Eric W. Biederman wrote:
> The classic challenge is that we really need most of the patches to go
> through other maintainers because they are not for subsystems we
> maintain.  So I am fairly certain things like our network namespace
> work will show up in linux-next because they show up in net-next-2.6.

But, there are things like the mqueue patches that are against areas
that really have no maintainers.  Do you think there will be many more
like that?  

-- Dave

  parent reply	other threads:[~2008-07-15 17:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 14:43 Feeding containers patches into linux-next Dave Hansen
2008-07-15 15:29 ` Serge E. Hallyn
     [not found]   ` <20080715152933.GA12061-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-07-15 17:50     ` Eric W. Biederman
     [not found]       ` <m1d4lff355.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
2008-07-15 17:55         ` Dave Hansen [this message]
2008-07-15 18:56           ` Eric W. Biederman
     [not found]             ` <m1fxqbc6y2.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
2008-07-15 19:07               ` Dave Hansen

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=1216144516.9459.7.camel@nimitz \
    --to=dave-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.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