From: Jakub Kicinski <kuba@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: 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 08:13:01 -0800 [thread overview]
Message-ID: <20250204081301.6fdb1536@kernel.org> (raw)
In-Reply-To: <20250204154938.GF22963@pendragon.ideasonboard.com>
On Tue, 4 Feb 2025 17:49:38 +0200 Laurent Pinchart wrote:
> Or apparently project or customer names for consulting companies:
>
> 29 Kory Maincent (Dent Project) <kory.maincent@bootlin.com>
> 34 Alexis Lothoré (eBPF Foundation) <alexis.lothore@bootlin.com>
FWIW these are customer names, indeed. Project/Foundation pays for
contracting work in both cases.
> The other cases correctly refer to companeis, for contributors using
> other email addresses:
>
> 14 linux.dev
> 41 zytor.com
> 47 joelfernandes.org
> 176 alien8.de
> 243 gmail.com
> 333 goodmis.org
> 454 armlinux.org.uk
> 918 infradead.org
> 1007 kernel.org
>
> Do we want to only document existing practices, or also tell which
> one(s) should be favoured ?
I'm hoping that documenting the most prevalent existing practice
will naturally make it favored. IOW I'd prefer to document just
one option. I don't really care which one we pick, but the brackets
seem most common.
next prev parent reply other threads:[~2025-02-04 16:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 17:46 [PATCH] docs: submitting-patches: document the format for affiliation 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 [this message]
2025-02-04 18:05 ` Randy Dunlap
2025-02-04 19:33 ` Jakub Kicinski
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=20250204081301.6fdb1536@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=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 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.