From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
Oleg Nesterov <oleg@redhat.com>,
Prarit Bhargava <prarit@redhat.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Josh Hunt <johunt@akamai.com>, Liu Hua <sdu.liu@huawei.com>,
Kees Cook <keescook@chromium.org>,
Aaron Tomlin <atomlin@redhat.com>,
Manfred Spraul <manfred@colorfullife.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Documentation/sysctl/kernel.txt: header
Date: Wed, 25 Feb 2015 20:23:48 +0100 [thread overview]
Message-ID: <54EE2144.7060709@gmx.de> (raw)
In-Reply-To: <20150225120114.005dec40@lwn.net>
On 25.02.2015 20:01, Jonathan Corbet wrote:
> On Wed, 25 Feb 2015 19:43:17 +0100
> Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
>
>> +For other authors see the commit history.
Yes I can delete it.
>> +
>> +For general info and disclaimer, please look in README.
>
> It generally seems fine, but the above text could just as reasonably be
> put into every file in the tree. How about if we just take it out?
>
> Thanks,
>
> jon
>
Most directories in Documentation do not have a README. So refering to
it seems ok.
I guess the chapter "Legal blurb" could be deleted from README. That
information is already in /COPYING.
So maybe we should replace
-For general info and legal blurb, please look in README.
by
+For an overview of sysctl, please look in README.
and in a separate patch remove the "Legal blurb" section from README.
Best regards
Heinrich
prev parent reply other threads:[~2015-02-25 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 18:43 [PATCH 1/1] Documentation/sysctl/kernel.txt: header Heinrich Schuchardt
2015-02-25 18:47 ` Kees Cook
2015-02-25 19:01 ` Jonathan Corbet
2015-02-25 19:23 ` Heinrich Schuchardt [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=54EE2144.7060709@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=atomlin@redhat.com \
--cc=corbet@lwn.net \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=johunt@akamai.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=oleg@redhat.com \
--cc=prarit@redhat.com \
--cc=sdu.liu@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox