From: Peter Korsgaard <peter@korsgaard.com>
To: Baruch Siach via buildroot <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Julien Olivain <ju.o@free.fr>,
Christian Stewart <christian@aperture.us>,
Vincent Fazio <vfazio@xes-inc.com>
Subject: Re: [Buildroot] [PATCH v1 1/1] package/mmc-utils: fix hash mismatch for readme file
Date: Thu, 12 Dec 2024 20:49:46 +0100 [thread overview]
Message-ID: <875xnowujp.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <878qsm7lwt.fsf@tarshish> (Baruch Siach via buildroot's message of "Wed, 11 Dec 2024 08:50:58 +0200")
>>>>> "Baruch" == Baruch Siach via buildroot <buildroot@buildroot.org> writes:
> Hi Christian,
> On Tue, Dec 10 2024, Christian Stewart via buildroot wrote:
>> Commit b03dc5: package/mmc-utils: bump to 523d8f3cfb21
>>
>> The README hash changed causing a build failure:
>>
>> https://github.com/skiffos/SkiffOS/actions/runs/12266361526/job/34224344838#step:8:60617
>>
>> Update the hash for the README.md file to fix the issue.
> The patch updates README hash. Is that a typo?
Ups, I missed your comment - Sorry about that.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-12-12 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 0:49 [Buildroot] [PATCH v1 1/1] package/mmc-utils: fix hash mismatch for readme file Christian Stewart via buildroot
2024-12-11 6:50 ` Baruch Siach via buildroot
2024-12-11 7:39 ` Christian Stewart via buildroot
2024-12-12 19:49 ` Peter Korsgaard [this message]
2024-12-11 8:11 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2024-12-11 13:33 Vincent Fazio
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=875xnowujp.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=vfazio@xes-inc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.