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 09:56:33 +0200	[thread overview]
Message-ID: <38f702d0-1b86-9612-e431-a43fcf960c4f@gmail.com> (raw)
In-Reply-To: <CANNYZj9a3Ks+P4LCx-A8cLwgku_Qjaw6ePwht1E8CSFuXtR1HA@mail.gmail.com>

Hi Alex,

On 10/16/22 09:24, Alexander Kanavin wrote:
> We are asking for help here with version updates. Specifically that you 
> take at least some of these reports and act on them. If you don’t want 
> to do this, fine, but demanding that those reports are not produced 
> because deleting them inconveniences you is both unreasonable and 
> antagonizing. Keeping core updated should not be ‘Alex problem’ but it 
> de facto is.
> 

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*.

> Alex
> 
> On Sun 16. Oct 2022 at 8.50, Jacob Kroon <jacob.kroon@gmail.com 
> <mailto:jacob.kroon@gmail.com>> wrote:
> 
>     Another AUH mail bomb, another time where I am pressing "delete" 148
>     times in my email client. I don't review machine generated emails.
>     I would not cry if AUH mails were sent to a designated mailing list,
>     one
>     that I am not subscribed to.
> 
>     Jacob
>

Jacob


  reply	other threads:[~2022-10-16  7:56 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 [this message]
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

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=38f702d0-1b86-9612-e431-a43fcf960c4f@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