Linux Documentation
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: 岳秉坤 <yuebingkun@kylinos.cn>,
	mchehab@kernel.org, tony.luck@intel.com, corbet@lwn.net,
	shiju.jose@huawei.com, jacopo.mondi@ideasonboard.com,
	laurent.pinchart@ideasonboard.com, hverkuil+cisco@kernel.org,
	sakari.ailus@linux.intel.com, linux-doc@vger.kernel.org,
	linux-edac@vger.kernel.org, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] Documentation: fix "should be use" grammar in ABI README
Date: Wed, 29 Jul 2026 01:15:45 +0800	[thread overview]
Message-ID: <amjjwfSimXeZOWbA@wyuan.org> (raw)
In-Reply-To: <b7773638-12dd-44a4-b075-2e6994dd9971@infradead.org>

On Tue, Jul 28, 2026 at 09:55:42AM -0700, Randy Dunlap wrote:
> > That is to say, when dealing with multiple authors, we suggest using
> > trailers to represent the sequence of authors in chronological order.
> > 
> > Then, this will facilitate subsequent readers to understand the
> > development history of the patch through the order of the trailers.(?)
> > 
> > And, aren't these subsequent examples merely confining the discussion to
> > these two trailers?
> 
> They seem to be but that's just a documentation deficiency IMO.

OK, let me take some time to look through the history of this file and
see if I can uncover any clues.

If this is indeed a flaw, it might be worth clarifying. That said, I am
not sure how many people actually find it ambiguous. In any case, it may
be better for someone with more experience to improve it, as I am
clearly not qualified to do so.

> > Besides the submitting-patches file, It seems to me that the probability
> > of "Signed-off-by" appearing on the last line is much higher than in
> > other cases. Is this a usual practice? It seems that everyone tacitly
> > agreed to write "Acked-by" and "Reviewed-by" at the top, even though
> > they occurred after "Sob".
> > 
> 
> I chose 2 files and looked at their "git log" history: MAINTAINERS and
> kernel/panic.c. In those files I see corroboration of my "claim," so I'm
> satisfied with it.

Makes sense. Perhaps different subsystems simply have different
preferences, then. My observation may not have been representative.

Thanks.

  reply	other threads:[~2026-07-28 17:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28  4:12 [PATCH v2 0/3] Documentation: fix a few typo and wording issues 岳秉坤
2026-07-28  4:12 ` [PATCH v2 1/3] Documentation: fix "should be use" grammar in ABI README 岳秉坤
2026-07-28  4:24   ` Weijie Yuan
2026-07-28  4:31     ` Randy Dunlap
2026-07-28  5:48       ` Weijie Yuan
2026-07-28 16:55         ` Randy Dunlap
2026-07-28 17:15           ` Weijie Yuan [this message]
2026-07-28 17:25             ` Luck, Tony
2026-07-28 17:51               ` Weijie Yuan
2026-07-28  4:12 ` [PATCH v2 2/3] Documentation: fix "readng" typo in EDAC memory-repair ABI doc 岳秉坤
2026-07-28  4:12 ` [PATCH v2 3/3] Documentation: fix "thare are" typo in V4L subdev routing doc 岳秉坤

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=amjjwfSimXeZOWbA@wyuan.org \
    --to=wy@wyuan.org \
    --cc=corbet@lwn.net \
    --cc=hverkuil+cisco@kernel.org \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=shiju.jose@huawei.com \
    --cc=tony.luck@intel.com \
    --cc=yuebingkun@kylinos.cn \
    /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