From: Daniel Lezcano <daniel.lezcano@free.fr>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Serge E. Hallyn" <serge.hallyn@canonical.com>,
Andrew Morton <akpm@linux-foundation.org>,
Paul Menage <menage@google.com>
Subject: Re: [Patch] doc: remove ns_cgroup from feature-removal-schedule.txt
Date: Tue, 07 Jun 2011 14:49:58 +0200 [thread overview]
Message-ID: <4DEE1E76.2060101@free.fr> (raw)
In-Reply-To: <20110607122233.GB3550@cr0>
On 06/07/2011 02:22 PM, Américo Wang wrote:
> On Tue, Jun 07, 2011 at 02:19:31PM +0200, Daniel Lezcano wrote:
>> On 06/07/2011 02:06 PM, Américo Wang wrote:
>>> In the following commit Daniel removed ns_cgroup
>>>
>>> commit a77aea92010acf54ad785047234418d5d68772e2
>>> Author: Daniel Lezcano<daniel.lezcano@free.fr>
>>> Date: Thu May 26 16:25:23 2011 -0700
>>>
>>> cgroup: remove the ns_cgroup
>>>
>>> but Daniel forgot to remove the related doc in feature-removal-schedule.txt.
>>> This patch removes that too.
>> Well, I am not sure we should remove this entry from the documentation.
> That is a list of features which will be removed,
> not for features that was in the kernel.
>
>> I let this in the doc because people may want to follow what was
>> removed and from what kernel version.
> We have changelogs or git logs, right? :)
Never mind.
The introduction in the doc file is clear:
"... When the feature is removed from the kernel, it should also
be removed from this file."
Sorry I missed this when removing the ns_cgroup.
Thanks for fixing it.
-- Daniel
prev parent reply other threads:[~2011-06-07 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 12:06 [Patch] doc: remove ns_cgroup from feature-removal-schedule.txt Américo Wang
2011-06-07 12:19 ` Daniel Lezcano
2011-06-07 12:22 ` Américo Wang
2011-06-07 12:49 ` Daniel Lezcano [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=4DEE1E76.2060101@free.fr \
--to=daniel.lezcano@free.fr \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=serge.hallyn@canonical.com \
--cc=xiyou.wangcong@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.