public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kir Kolyshkin <kir@openvz.org>
To: Daniel Lezcano <dlezcano@fr.ibm.com>
Cc: Pavel Emelyanov <xemul@openvz.org>,
	Linux Containers <containers@lists.osdl.org>,
	Cedric Le Goater <clg@fr.ibm.com>, Theodore Tso <tytso@mit.edu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Devel] Re: [PATCH][DOCUMENTATION] The namespaces compatibility list doc
Date: Wed, 21 Nov 2007 15:33:59 +0300	[thread overview]
Message-ID: <474425B7.3000808@openvz.org> (raw)
In-Reply-To: <473DBCC2.70506@fr.ibm.com>

Daniel Lezcano wrote:
> Pavel Emelyanov wrote:
>>
>> +2. Intentionnaly, two equal user ids in different user namespaces
>       Intentionaly
Intentionally 

      parent reply	other threads:[~2007-11-21 12:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16  9:34 [PATCH][DOCUMENTATION] The namespaces compatibility list doc Pavel Emelyanov
2007-11-16 15:52 ` Daniel Lezcano
2007-11-16 16:11   ` Pavel Emelyanov
2007-11-16 16:48   ` Randy Dunlap
2007-11-21 12:33   ` Kir Kolyshkin [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=474425B7.3000808@openvz.org \
    --to=kir@openvz.org \
    --cc=clg@fr.ibm.com \
    --cc=containers@lists.osdl.org \
    --cc=dlezcano@fr.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=xemul@openvz.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