From: Jakub Kicinski <kuba@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
corbet@lwn.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: submitting-patches: document the format for affiliation
Date: Tue, 4 Feb 2025 11:33:42 -0800 [thread overview]
Message-ID: <20250204113342.3b8f18f8@kernel.org> (raw)
In-Reply-To: <4f27a0db-256c-4792-a957-1387de9dc56e@infradead.org>
On Tue, 4 Feb 2025 10:05:12 -0800 Randy Dunlap wrote:
> Signed-off-by: John Doe <jdoe@example.com> # Company
Interesting :)
On a quick look this seems to be the format of choice for maintainers
who edit patches:
Signed-off-by: Mr Maintainer <jdoe@example.com> # fixed xyz
I don't see a single # use in the From lines. I think the # formatting
is well suited for free form comments. Less so for things which may need
to be machine readable (for development statistics).
next prev parent reply other threads:[~2025-02-04 19:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 17:46 Jakub Kicinski
2025-02-04 7:59 ` Geert Uytterhoeven
2025-02-04 15:18 ` Jakub Kicinski
2025-02-04 15:49 ` Laurent Pinchart
2025-02-04 16:13 ` Jakub Kicinski
2025-02-04 18:05 ` Randy Dunlap
2025-02-04 19:33 ` Jakub Kicinski [this message]
2025-02-04 19:43 ` Geert Uytterhoeven
2025-02-04 19:43 ` Konstantin Ryabitsev
2025-02-05 7:37 ` Yanteng Si
2025-02-05 14:23 ` Krzysztof Kozlowski
2025-02-05 14:52 ` Yanteng Si
2025-02-05 14:57 ` Krzysztof Kozlowski
2025-02-06 8:21 ` Yanteng Si
2025-02-10 18:38 ` Jonathan Corbet
2025-02-10 18:45 ` Konstantin Ryabitsev
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=20250204113342.3b8f18f8@kernel.org \
--to=kuba@kernel.org \
--cc=corbet@lwn.net \
--cc=geert@linux-m68k.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=workflows@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