All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] docs: Make CodingStyle and SubmittingPatches symlinks
Date: Mon, 23 Jan 2017 02:54:19 -0800	[thread overview]
Message-ID: <1485168859.12563.29.camel@perches.com> (raw)
In-Reply-To: <CAMuHMdX50mLnApEvQzUGq-WMcSq0R_XFqX52T7DrAKjtWDofdg@mail.gmail.com>

On Mon, 2017-01-23 at 11:44 +0100, Geert Uytterhoeven wrote:
> When will/can we get rid of them?
> Old (doh) kernels, and new versions of stable kernels will keep on having
> them for the next +10 years.
> 
> To me, these[*] filenames are more like a user-visible API, which should
> not be changed without given consideration.

Yup.

  reply	other threads:[~2017-01-23 10:54 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
2017-01-23 10:34     ` Mauro Carvalho Chehab
2017-01-23 10:44       ` Geert Uytterhoeven
2017-01-23 10:54         ` Joe Perches [this message]
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=1485168859.12563.29.camel@perches.com \
    --to=joe@perches.com \
    --cc=corbet@lwn.net \
    --cc=geert@linux-m68k.org \
    --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 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.