workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: 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 07:18:34 -0800	[thread overview]
Message-ID: <20250204071834.78e0ffb1@kernel.org> (raw)
In-Reply-To: <CAMuHMdXXNkpWjkKvMLd-MF=npzqJXMtnXkaba60JY7hCzyjz7g@mail.gmail.com>

On Tue, 4 Feb 2025 08:59:28 +0100 Geert Uytterhoeven wrote:
> You probably also want to document the other popular[*] solution:
> 
>     From: Patch Author <author+company@example.com>
> 
> [*] Statistics for v6.0..v6.14-rc1:
>       - "(Company): 3430
>       - "+company": 2871

Hm, I mostly associate that format with MAINTAINERS entries where
people want email classification. But you're right there are some 
uses, only 3 of them look like companies, tho.

$ git log --format='%ae' v6.0..v6.14-rc1 | grep '+' | sed -e 's/.*+\(.*\)@.*/\1/' | sort | uniq -c | awk '{if ($1 > 5) print;}'
     18 huawei
    464 kernel
     46 lin
    742 linaro
      8 publicgit
   1646 renesas

$ git log --format='%an' v6.0..v6.14-rc1 | sed -n 's/.*(\(.*\))/\1/p' | sort | uniq -c | awk '{if ($1 > 5) print;}'
    177 AMD
    210 Arm
     29 Dent Project
     37 eBPF Foundation
    547 Google
     13 Hanghong Ma
    132 IBM
     46 Intel
     38 Microsoft
     18 Ming Qiang Wu
    155 NGI0
     26 NXP OSS
   1487 Oracle
     19 OSS
      7 Som
     70 Sony
    353 SUSE
      9 tencent
     24 VMware
      8 辛安文


  reply	other threads:[~2025-02-04 15:18 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 [this message]
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
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=20250204071834.78e0ffb1@kernel.org \
    --to=kuba@kernel.org \
    --cc=corbet@lwn.net \
    --cc=geert@linux-m68k.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox