linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Alex Shi <alex.shi@linux.alibaba.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org,
	linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
	linux-samsung-soc@vger.kernel.org, linux-ia64@vger.kernel.org,
	linux-mips@vger.kernel.org, linux-parisc@vger.kernel.org,
	linux-scsi@vger.kernel.org, linux-s390@vger.kernel.org,
	kvm@vger.kernel.org, linux-sh@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH 01/12] Documentation: move architectures together
Date: Fri, 12 Jul 2019 11:34:27 -0600	[thread overview]
Message-ID: <20190712113427.62fa7ffc@lwn.net> (raw)
In-Reply-To: <20190712022018.27989-1-alex.shi@linux.alibaba.com>

On Fri, 12 Jul 2019 10:20:07 +0800
Alex Shi <alex.shi@linux.alibaba.com> wrote:

> There are many different archs in Documentation/ dir, it's better to
> move them together in 'Documentation/arch' which follows from kernel source.

So this seems certain to collide badly with Mauro's RST-conversion monster
patch set.

More to the point, though...if we are going to thrash up things this
badly, we want to be sure that we're doing it right so we don't end up
renaming everything again.  Grouping stuff into a new arch/ subdirectory
adds a bit of order, but it doesn't do much toward trying to organize our
documentation for its readers, and it doesn't help us to modernize the
docs and get rid of the old, useless stuff.  A quick check shows that many
of these files have seen no changes other than typo fixes since the
beginning of the Git era.

So, in my mind, this needs some thought.  Maybe we want a
Documentation/arch in the end, but I'm not convinced that we should just
create it and fill it with a snow shovel.  This might be a good thing to
discuss at the kernel summit in September.

Thanks,

jon

  parent reply	other threads:[~2019-07-12 17:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12  2:20 [PATCH 01/12] Documentation: move architectures together Alex Shi
2019-07-12  2:20 ` [PATCH 02/12] Documentation/arm: repointer docs to Documentation/arch/arm Alex Shi
2019-07-16 14:51   ` Krzysztof Kozlowski
2019-07-12  2:20 ` [PATCH 03/12] Documentation/ia64: repointer docs to Documentation/arch/ia64 Alex Shi
2019-07-12  2:20 ` [PATCH 04/12] Documentation/m68k: repointer docs to Documentation/arch/ Alex Shi
2019-07-12  2:20 ` [PATCH 05/12] Documentation/s390: " Alex Shi
2019-07-12  2:20 ` [PATCH 06/12] Documentation/mips: " Alex Shi
2019-07-12  2:20 ` [PATCH 07/12] Documentation/parisc: " Alex Shi
2019-07-12  2:20 ` [PATCH 08/12] Dcumentation/powerpc: " Alex Shi
2019-07-12  2:20 ` [PATCH 09/12] Dcumentation/sh: " Alex Shi
2019-07-12  2:20 ` [PATCH 10/12] Documentation/sparc: " Alex Shi
2019-07-12  2:20 ` [PATCH 11/12] Documentation/x86: " Alex Shi
2019-07-12  2:20 ` [PATCH 12/12] Documentation/xtensa: " Alex Shi
2019-07-12 17:34 ` Jonathan Corbet [this message]
2019-07-14 15:21   ` [PATCH 01/12] Documentation: move architectures together Alex Shi

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=20190712113427.62fa7ffc@lwn.net \
    --to=corbet@lwn.net \
    --cc=alex.shi@linux.alibaba.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).