From: lilmike <lilmike@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rpi-firmware: please update
Date: Tue, 13 Jun 2023 20:38:35 +0200 [thread overview]
Message-ID: <20230613183835.Z3e4Lb8f6CC-UUFEdSqsN50umttgWKn4kKqAzgfP0Z8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44408@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
New comment by lilmike on void-packages repository
https://github.com/void-linux/void-packages/issues/44408#issuecomment-1589838902
Comment:
I did a full update on the image, plus adding in the repository you
built, so if those packages are installed on the image and are in your
repo then they did get updated.
-Michael.
On Tue, Jun 13, 2023 at 09:54:09AM -0700, classabbyamp wrote:
>did the image just have the updated rpi-firmware package or also the rpi-kernel and rpi-userland updates?
>
>--
>Reply to this email directly or view it on GitHub:
>https://github.com/void-linux/void-packages/issues/44408#issuecomment-1589688953
>You are receiving this because you were mentioned.
>
>Message ID: ***@***.***>
--
Sorry about the test, it's just a me thing.
Michael Taboada, Creator of Games. Does that make me a god, well, sorta.
My pgp key: 79BC390E8864CD71305D4DD606CD2197A6EE5ED7
My website: https://michaels.world
2MB website: https://2mb.games
Don't believe everything you read on the internet. I might not be real, you might not be real, and this email certainly isn't real.
Sent from my christmas spirited...
stationary bicycle
next prev parent reply other threads:[~2023-06-13 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 13:36 [ISSUE] " lilmike
2023-06-13 14:47 ` classabbyamp
2023-06-13 16:50 ` hjozwiak
2023-06-13 16:51 ` hjozwiak
2023-06-13 18:38 ` lilmike [this message]
2023-10-30 20:42 ` [ISSUE] [CLOSED] " classabbyamp
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=20230613183835.Z3e4Lb8f6CC-UUFEdSqsN50umttgWKn4kKqAzgfP0Z8@z \
--to=lilmike@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).