From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux regressions mailing list <regressions@lists.linux.dev>,
Ard Biesheuvel <ardb@kernel.org>, Borislav Petkov <bp@alien8.de>
Cc: bwg <whirl@mniotilta.ca>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-efi <linux-efi@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
shibedrill1@gmail.com
Subject: Re: Fwd: Kernel 6.6.1 hangs on "loading initial ramdisk"
Date: Sun, 10 Dec 2023 11:17:16 +0100 [thread overview]
Message-ID: <01fe1a4d-a346-4ddd-bd1c-22182ed0e60a@leemhuis.info> (raw)
In-Reply-To: <7cf21703-391a-4123-b862-14a1af62aeaa@gmail.com>
On 10.12.23 08:30, Bagas Sanjaya wrote:
> On 12/10/23 14:15, Linux regression tracking (Thorsten Leemhuis) wrote:
[...]
>> [1] This is why: You just added Ard and Boris to the CC, but did not
>> make it obvious *why* they should care about that mail. They (and all
>> the other recipients) for sure will have no idea what a1b87d54f4e45f
>> exactly is, so you should have mentioned the commit summary. And doing
>> that after a big quote makes it worse, as many people now need to scroll
>> down to see if that mails contains something that might be relevant for
>> them -- and just a waste of time if not.
>>
>> Furthermore, sending the first mail of the thread to all those people
>> and lists was likely not very wise, as nobody is likely to care in a
>> case like this. And not removing all those people and lists in the
>> second mail of the thread make it a lot worse, as it became clear that
>> many people and list do not care about it now that the regression was
>> bisected. Hence it's best to remove them, we all get enough mail already.
>>
>> All that makes people ignore mails from you -- and maybe about
>> regression tracking in general. :-(
>
> Oops, I didn't greet additional Cc's as you mentioned (that's my
> tendency when handling regressions).
Well, yes, but as mentioned that is just one of several things that
were slightly off.
> So maybe we continue tracking this on Bugzilla or keeping on ML or
> both?
Not sure what you mean. I'll reply in private, no need to bother the
others with even more mail.
BTW: Ard, I noticed you got involved in the ticket. Thx for that!
Ciao, Thorsten
prev parent reply other threads:[~2023-12-10 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9057d7de-f2e0-44ba-bec7-8b0861b2a850@gmail.com>
[not found] ` <ZXVdZE3D-KFBqPnj@archie.me>
2023-12-10 7:15 ` Fwd: Kernel 6.6.1 hangs on "loading initial ramdisk" Linux regression tracking (Thorsten Leemhuis)
2023-12-10 7:30 ` Bagas Sanjaya
2023-12-10 10:17 ` Thorsten Leemhuis [this message]
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=01fe1a4d-a346-4ddd-bd1c-22182ed0e60a@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=ardb@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=shibedrill1@gmail.com \
--cc=tglx@linutronix.de \
--cc=whirl@mniotilta.ca \
--cc=x86@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).