* linux-next: stats (Was: Linux 6.0-rc1) [not found] <CAHk-=wgRFjPHV-Y_eKP9wQMLFDgG+dEUHiv5wC17OQHsG5z7BA@mail.gmail.com> @ 2022-08-15 2:50 ` Stephen Rothwell 2022-08-17 14:41 ` Geert Uytterhoeven 0 siblings, 1 reply; 2+ messages in thread From: Stephen Rothwell @ 2022-08-15 2:50 UTC (permalink / raw) To: Linus Torvalds; +Cc: Linux Kernel Mailing List, Linux Next Mailing List [-- Attachment #1: Type: text/plain, Size: 2510 bytes --] Hi all, As usual, the executive friendly graph is at http://neuling.org/linux-next-size.html :-) (No merge commits counted, next-20220802 was the first linux-next after the merge window opened.) Commits in v6.0-rc1 (relative to v5.19): 13543 Commits in next-20220802: 13109 Commits with the same SHA1: 12468 Commits with the same patch_id: 309 (1) Commits with the same subject line: 12 (1) (1) not counting those in the lines above. So commits in -rc1 that were in next-20220802: 12789 94% Some breakdown of the list of extra commits (relative to next-20220802) in -rc1: Top ten first word of commit summary: 95 perf 33 dt-bindings 30 tools 25 net 24 kvm 23 virtio_ring 19 riscv 19 cxl 19 ceph 18 bpf Top ten authors: 43 xuanzhuo@linux•alibaba.com 25 irogers@google•com 17 krzysztof.kozlowski@linaro•org 15 conor.dooley@microchip•com 14 leo.yan@linaro•org 13 xiubli@redhat•com 13 dan.j.williams@intel•com 11 zhengjun.xing@linux•intel.com 11 namhyung@kernel•org 10 snitzer@kernel•org Top ten commiters: 107 acme@redhat•com 78 mst@redhat•com 58 kuba@kernel•org 43 palmer@rivosinc•com 26 pbonzini@redhat•com 24 idryomov@gmail•com 20 dan.j.williams@intel•com 18 ast@kernel•org 17 tiwai@suse•de 17 len.brown@intel•com There are also 320 commits in next-20220802 that didn't make it into v6.0-rc1. Top ten first word of commit summary: 29 tools 27 thermal 22 arm 20 mm 20 fs 15 arm64 14 soc 13 dt-bindings 10 rust 9 btrfs Top ten authors: 29 paulmck@kernel•org 19 ojeda@kernel•org 18 zokeefe@google•com 11 marex@denx•de 10 daniel.lezcano@linexp•org 8 windhl@126•com 8 wedsonaf@google•com 7 iangelak@fb•com 7 daniel.lezcano@linaro•org 7 broonie@kernel•org Top ten commiters: 43 daniel.lezcano@linaro•org 32 ojeda@kernel•org 32 akpm@linux-foundation•org 29 paulmck@kernel•org 18 almaz.alexandrovich@paragon-software•com 13 geert+renesas@glider•be 12 alexandre.torgue@foss•st.com 11 broonie@kernel•org 9 srinivas.kandagatla@linaro•org 8 treding@nvidia•com -- Cheers, Stephen Rothwell [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --] ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: linux-next: stats (Was: Linux 6.0-rc1) 2022-08-15 2:50 ` linux-next: stats (Was: Linux 6.0-rc1) Stephen Rothwell @ 2022-08-17 14:41 ` Geert Uytterhoeven 0 siblings, 0 replies; 2+ messages in thread From: Geert Uytterhoeven @ 2022-08-17 14:41 UTC (permalink / raw) To: Stephen Rothwell Cc: Linus Torvalds, Linux Kernel Mailing List, Linux Next Mailing List Hi Stephen, On Mon, Aug 15, 2022 at 4:55 AM Stephen Rothwell <sfr@canb•auug.org.au> wrote: > There are also 320 commits in next-20220802 that didn't make it into > v6.0-rc1. > Top ten commiters: > 13 geert+renesas@glider•be How did that happen? Turns out these are false positives. Whenever I update any of the renesas-*-for-vX.Y branches, I merge them into renesas-next, which is pulled into linux-next. When a commit in a renesas-*-for-vX.Y branch turns out to be bad, and the branch hasn't been pulled by soc yet, I just fix that by rebasing the renesas-*-for-vX.Y branch, and resolving any conflicts during the next merge into renesas-next. So the bad commits are gone from the renesas-*-for-vX.Y branches, and thus will never go upstream, but technically, they are still part of linux-next. Hence they show up in the statistics you do not want to be part of... Perhaps I should just recreate renesas-next every time any of the renesas-*-for-vX.Y branches needs to be rebased? I already recreate renesas-next after each rc1 release. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k•org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-08-17 14:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CAHk-=wgRFjPHV-Y_eKP9wQMLFDgG+dEUHiv5wC17OQHsG5z7BA@mail.gmail.com>
2022-08-15 2:50 ` linux-next: stats (Was: Linux 6.0-rc1) Stephen Rothwell
2022-08-17 14:41 ` Geert Uytterhoeven
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox