From: Geert Uytterhoeven <firstname.lastname@example.org>
To: Stephen Rothwell <email@example.com>
Cc: Linus Torvalds <firstname.lastname@example.org>,
Linux Kernel Mailing List <email@example.com>,
Linux Next Mailing List <firstname.lastname@example.org>
Subject: Re: linux-next: stats (Was: Linux 6.0-rc1)
Date: Wed, 17 Aug 2022 16:41:18 +0200 [thread overview]
Message-ID: <CAMuHMdXoVzcVERZQXDYxDZZc2_=huaAF8dC8o4iksV07w8ZU7Q@mail.gmail.com> (raw)
On Mon, Aug 15, 2022 at 4:55 AM Stephen Rothwell <email@example.com> wrote:
> There are also 320 commits in next-20220802 that didn't make it into
> Top ten commiters:
> 13 firstname.lastname@example.org
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.
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- email@example.com
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
next prev parent reply other threads:[~2022-08-17 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 23:41 Linux 6.0-rc1 Linus Torvalds
2022-08-15 1:23 ` Kirill A. Shutemov
2022-08-15 2:27 ` Steven Rostedt
2022-08-15 2:50 ` linux-next: stats (Was: Linux 6.0-rc1) Stephen Rothwell
2022-08-17 14:41 ` Geert Uytterhoeven [this message]
2022-08-15 18:04 ` Build regressions/improvements in v6.0-rc1 Geert Uytterhoeven
2022-08-15 18:10 ` Geert Uytterhoeven
2022-08-15 23:48 ` Linux 6.0-rc1 Guenter Roeck
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).