From: weibu@redadmin.org
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Akira Yokosawa <akiyks@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] docs: submitting-patches: Fix section structure around DCO
Date: Thu, 09 Jul 2026 19:34:15 +0900 [thread overview]
Message-ID: <e942938989f17a884019324412d33031@redadmin.org> (raw)
In-Reply-To: <1bf78dca-1651-4173-938c-d76b3c8db229@infradead.org>
Maybe it would be better to send this as a follow-up patch after the
original patch is merged, to avoid unnecessary churn.
Thanks,
Akiyoshi Kurita
2026-07-09 06:04 に Randy Dunlap さんは書きました:
> Hi,
>
> On 7/2/26 3:44 AM, Akira Yokosawa wrote:
>> Commit 5903019b2a5e ("Documentation/SubmittingPatches: convert it to
>> ReST markup") made "DCO 1.1" a subsection under the section "Sign your
>> work - ...". However, the DCO text is meant to be referenced in the
>> section.
>>
>> Furthermore, in HTML and PDF docs, paragraphs following the DCO:
>>
>> then you just add a line saying:
>>
>> Signed-off-by: [...]
>>
>> [...]
>> as it was propagated to the maintainers and ultimately to Linus,
>> with
>> the first SoB entry signalling primary authorship of a single
>> author.
>>
>> appear to belong to the DCO, rather than to "Sign your work - ..."
>> where it should.
>>
>> In reST (and other documentation tools), once you start a subsection
>> under a section, there is no way to go back to the section.
>>
>> Fix the section structure by making the DCO a literal block, with
>> indent changes made in commit 5903019b2a5e reverted.
>
> I don't see much difference in the before and after HTML
> other than the use of literal blocks, which do make it a
> small bit clearer where the DCO/Reviewer's blocks are.
>
> Tested-by: Randy Dunlap <rdunlap@infradead.org>
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
>
> Thanks.
>
>> While at it, fix the same issue at "Reviewer's statement of
>> oversight".
>>
>> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
>> ---
>> Documentation/process/submitting-patches.rst | 14 ++++++--------
>> 1 file changed, 6 insertions(+), 8 deletions(-)
next prev parent reply other threads:[~2026-07-09 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 10:44 [PATCH -next] docs: submitting-patches: Fix section structure around DCO Akira Yokosawa
2026-07-08 21:04 ` Randy Dunlap
2026-07-09 10:34 ` weibu [this message]
2026-07-09 14:44 ` Akira Yokosawa
2026-07-09 14:50 ` weibu
2026-07-10 19:46 ` 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=e942938989f17a884019324412d33031@redadmin.org \
--to=weibu@redadmin.org \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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 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.