public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Jacob Kroon <jacob.kroon@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Ross Burton <ross.burton@arm.com>,
	Alexander Kanavin <alex.kanavin@gmail.com>
Subject: Re: [OE-core] [AUH] acpid: upgrading to 2.0.34 SUCCEEDED
Date: Sun, 16 Oct 2022 08:50:52 +0200	[thread overview]
Message-ID: <0171f109-2941-3269-3bd5-adf497e30e59@gmail.com> (raw)
In-Reply-To: <01010183ddac296d-fddf5612-f98f-47a4-99db-94cd829db3ba-000000@us-west-2.amazonses.com>

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

On 10/16/22 00:03, Auto Upgrade Helper wrote:
> Hello,
> 
> this email is a notification from the Auto Upgrade Helper
> that the automatic attempt to upgrade the recipe *acpid* to *2.0.34* has Succeeded.
> 
> Next steps:
>      - apply the patch: git am 0001-acpid-upgrade-2.0.33-2.0.34.patch
>      - check the changes to upstream patches and summarize them in the commit message,
>      - compile an image that contains the package
>      - perform some basic sanity tests
>      - amend the patch and sign it off: git commit -s --reset-author --amend
>      - send it to the appropriate mailing list
> 
> Alternatively, if you believe the recipe should not be upgraded at this time,
> you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
> automatic upgrades would no longer be attempted.
> 
> Please review the attached files for further information and build/update failures.
> Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
> 
> Regards,
> The Upgrade Helper
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#171742): https://lists.openembedded.org/g/openembedded-core/message/171742
> Mute This Topic: https://lists.openembedded.org/mt/94354924/4454410
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [jacob.kroon@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


  reply	other threads:[~2022-10-16  6:51 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 ` Jacob Kroon [this message]
2022-10-16  7:24   ` [OE-core] " 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

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=0171f109-2941-3269-3bd5-adf497e30e59@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