public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Jacob Kroon <jacob.kroon@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Ross Burton <ross.burton@arm.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [AUH] acpid: upgrading to 2.0.34 SUCCEEDED
Date: Sun, 16 Oct 2022 16:14:43 +0200	[thread overview]
Message-ID: <9536ebc8-dac6-3e93-fd6f-d6d804e75569@gmail.com> (raw)
In-Reply-To: <CANNYZj-wE01Eei1eEHOoywngiBO6Sgp_gp3fLxDQEFYAzuPE6w@mail.gmail.com>

On 10/16/22 14:05, Alexander Kanavin wrote:
> On Sun, 16 Oct 2022 at 09:56, Jacob Kroon <jacob.kroon@gmail.com> wrote:
>> I do think it is reasonable to ask for not being mail-bombed with
>> machine generated emails.
>>
>> I am asking for either to:
>> * put them on a separate mailing list
>> * merge them into one email
>>
>> If keeping core updated still is "Alex's problem" then the AUH emails
>> are not having the intended effect *anyway*.
> 
> They do help, just not to the level I would like. They also provide an
> easy way for someone who is not yet a contributor to become one,
> particularly when AUH did succeed and produced a working patch that
> doesn't need manual fixing. They also make the maintenance problem
> known and visible. Sweeping it all under the carpet as suggested would
> make the situation worse, not better.
> 

Don't put words in my mouth. I gave two alternatives, not to sweep them 
under the carpet. A third option would be to publish the AUH results on 
some webpage and post the link.

> If you do not want to mix those emails with those written by humans, I
> trust your email client has a filter system. I still cling to the
> belief that you would want to help the core, and only personal
> circumstances prevent you, and therefore this filter will be set to
> put those mails into a separate folder instead of deleting them
> ouright.

Fine, I'll setup filtering to forward all AUH emails to the trashbin then.

Jacob


      parent reply	other threads:[~2022-10-16 14:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-15 22:03 [AUH] acpid: upgrading to 2.0.34 SUCCEEDED auh
2022-10-16  6:50 ` [OE-core] " Jacob Kroon
2022-10-16  7:24   ` Alexander Kanavin
2022-10-16  7:56     ` Jacob Kroon
2022-10-16 12:05       ` Alexander Kanavin
2022-10-16 13:57         ` Bruce Ashfield
2022-10-16 13:58           ` Bruce Ashfield
2022-10-16 14:14         ` Jacob Kroon [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=9536ebc8-dac6-3e93-fd6f-d6d804e75569@gmail.com \
    --to=jacob.kroon@gmail.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@arm.com \
    /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