From: Jonathan Corbet <corbet@lwn.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 4/4] docs: move m68k architecture documentation under Documentation/arch/
Date: Fri, 31 Mar 2023 07:02:31 -0600 [thread overview]
Message-ID: <87cz4pdqfs.fsf@meer.lwn.net> (raw)
In-Reply-To: <CAMuHMdU=yyEciJD6iU-g90T3Qxg+t27Vz6VuojkhbxdODDJGwA@mail.gmail.com>
Geert Uytterhoeven <geert@linux-m68k.org> writes:
>> diff --git a/Documentation/translations/zh_CN/arch/parisc/debugging.rst b/Documentation/translations/zh_CN/arch/parisc/debugging.rst
>> index 9bd197eb0d41..c6b9de6d3175 100644
>> --- a/Documentation/translations/zh_CN/arch/parisc/debugging.rst
>> +++ b/Documentation/translations/zh_CN/arch/parisc/debugging.rst
>> @@ -1,4 +1,4 @@
>> -.. include:: ../disclaimer-zh_CN.rst
>> +.. include:: ../../disclaimer-zh_CN.rst
>>
>> :Original: Documentation/arch/parisc/debugging.rst
>>
>> diff --git a/Documentation/translations/zh_CN/arch/parisc/index.rst b/Documentation/translations/zh_CN/arch/parisc/index.rst
>> index 848742539550..9f69283bd1c9 100644
>> --- a/Documentation/translations/zh_CN/arch/parisc/index.rst
>> +++ b/Documentation/translations/zh_CN/arch/parisc/index.rst
>> @@ -1,5 +1,5 @@
>> .. SPDX-License-Identifier: GPL-2.0
>> -.. include:: ../disclaimer-zh_CN.rst
>> +.. include:: ../../disclaimer-zh_CN.rst
>>
>> :Original: Documentation/arch/parisc/index.rst
>>
>> diff --git a/Documentation/translations/zh_CN/arch/parisc/registers.rst b/Documentation/translations/zh_CN/arch/parisc/registers.rst
>> index caf5f258248b..a55250afcc27 100644
>> --- a/Documentation/translations/zh_CN/arch/parisc/registers.rst
>> +++ b/Documentation/translations/zh_CN/arch/parisc/registers.rst
>> @@ -1,4 +1,4 @@
>> -.. include:: ../disclaimer-zh_CN.rst
>> +.. include:: ../../disclaimer-zh_CN.rst
>>
>> :Original: Documentation/arch/parisc/registers.rst
>>
>
> These changes do not belong in this patch.
Why not? If I don't make those changes when moving the files, the
documentation build will break.
Thanks,
jon
next prev parent reply other threads:[~2023-03-31 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 19:56 [PATCH 0/4] docs: move yet more architecture docs Jonathan Corbet
2023-03-30 19:56 ` [PATCH 1/4] docs: Move arc architecture docs under Documentation/arch/ Jonathan Corbet
2023-04-02 6:44 ` Vineet Gupta
2023-03-30 19:56 ` [PATCH 2/4] docs: move ia64 " Jonathan Corbet
2023-03-30 19:56 ` [PATCH 3/4] docs: move parisc documentation " Jonathan Corbet
2023-04-01 6:43 ` Yanteng Si
2023-03-30 19:56 ` [PATCH 4/4] docs: move m68k architecture " Jonathan Corbet
2023-03-31 7:44 ` Geert Uytterhoeven
2023-03-31 13:02 ` Jonathan Corbet [this message]
2023-03-31 13:03 ` Jonathan Corbet
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=87cz4pdqfs.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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