From: Jani Nikula <jani.nikula@linux.intel.com>
To: Joe Perches <joe@perches.com>, Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: Make CodingStyle and SubmittingPatches symlinks
Date: Wed, 11 Jan 2017 11:45:11 +0200 [thread overview]
Message-ID: <87h9567wwo.fsf@intel.com> (raw)
In-Reply-To: <1484127081.12006.21.camel@perches.com>
On Wed, 11 Jan 2017, Joe Perches <joe@perches.com> wrote:
> On Wed, 2017-01-11 at 10:54 +0200, Jani Nikula wrote:
>> On Wed, 11 Jan 2017, Joe Perches <joe@perches.com> wrote:
>> > Make these files symlinks to the .rst equivalents
>>
>> If we're going to do this (and I really don't mind either way), then
>> please add
>>
>> Fixes: 08a9a8d44c1c ("doc: re-add CodingStyle and SubmittingPatches")
With this I'm merely saying that wherever 08a9a8d44c1c ends up, this
patch should end up too (if we want symlinks that is). There's enough
confusion with the renames already, I'd like to ensure that v4.10
doesn't end up having one thing, and the future another.
BR,
Jani.
>
> I don't believe this patch "fixes" the other, it just makes it
> possible to continue to write "Read Documentation/CodingStyle"
> or "Read Documentation/SubmittingPatches" to people that
> submit poorly formatted or improper patches.
>
> I attempted to do that a bit ago but then had to write out the
> Documentation/process/<foo>.rst equivalents instead.
>
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2017-01-11 9:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 22:09 [PATCH] docs: Make CodingStyle and SubmittingPatches symlinks Joe Perches
2017-01-11 8:54 ` Jani Nikula
2017-01-11 9:31 ` Joe Perches
2017-01-11 9:45 ` Jani Nikula [this message]
2017-01-13 19:41 ` Jonathan Corbet
2017-01-13 20:03 ` Joe Perches
2017-01-23 10:34 ` Mauro Carvalho Chehab
2017-01-23 10:44 ` Geert Uytterhoeven
2017-01-23 10:54 ` Joe Perches
2017-01-23 13:01 ` Mauro Carvalho Chehab
2017-01-23 13:25 ` Geert Uytterhoeven
2017-02-14 21:34 ` Jonathan Corbet
2017-02-14 21:37 ` Joe Perches
2017-02-24 7:50 ` Daniel Vetter
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=87h9567wwo.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=corbet@lwn.net \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@s-opensource.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