From: Joe Perches <joe@perches.com>
To: 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: Fri, 13 Jan 2017 12:03:24 -0800 [thread overview]
Message-ID: <1484337804.3065.36.camel@perches.com> (raw)
In-Reply-To: <20170113124135.7873b9c7@lwn.net>
On Fri, 2017-01-13 at 12:41 -0700, Jonathan Corbet wrote:
> On Tue, 10 Jan 2017 14:09:51 -0800
> Joe Perches <joe@perches.com> wrote:
>
> > Make these files symlinks to the .rst equivalents
>
> So I am not necessarily opposed to doing this, but the changelog lacks
> one important thing: why do we need to make that change? Have the
> existing one-liner files been a problem somehow?
The files tell people to open other files.
Giving the old link to people just tells them to
use the new filename instead.
symlinks open the new file automatically.
$ head Documentation/CodingStyle
This file has moved to process/coding-style.rst
vs a symlink
$ head Documentation/CodingStyle
.. _codingstyle:
Linux kernel coding style
=========================
This is a short document describing the preferred coding style for the
linux kernel. Coding style is very personal, and I won't **force** my
views on anybody, but this is what goes for anything that I have to be
able to maintain, and I'd prefer it for most other things too. Please
at least consider the points made here.
next prev parent reply other threads:[~2017-01-13 20:03 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
2017-01-13 19:41 ` Jonathan Corbet
2017-01-13 20:03 ` Joe Perches [this message]
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=1484337804.3065.36.camel@perches.com \
--to=joe@perches.com \
--cc=corbet@lwn.net \
--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