From: Peter Korsgaard <peter@korsgaard.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: kilian.zinnecker@mail.de, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] configs/rock5b: add hash for custom kernel, uboot
Date: Mon, 08 Jan 2024 12:06:13 +0100 [thread overview]
Message-ID: <87le90xexm.fsf@48ers.dk> (raw)
In-Reply-To: <ZYcqdkBK1XbKOmlq@landeda> (Yann E. MORIN's message of "Sat, 23 Dec 2023 19:44:06 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Hello,
> Now I realise one point that I completely forgot: if the upstream git
> tree disapears, we're left with downloading from a backup mirror (like
> s.b.o.). Or one can also use a primary mirror. In thoses cases, we do
> want to have a hash for the archive, even if the official is a git-clone
> repos.
> So, bottom line: we need a hash for all cases. Except when the remote is
> known to not be reproducible by design, which will be the few
> excpetions.
I agree.
> I initially dropped the kernel part when applying your patch. But in
> light of what I wrote above, I'll push a follow up patch fixing it,
> sorry for the mess...
> [0] https://lore.kernel.org/buildroot/874jgpnn7d.fsf@48ers.dk/
Committed those two patches to 2023.11.x as well, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-01-08 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 19:25 [Buildroot] [PATCH 1/1] configs/rock5b: add hash for custom kernel, uboot kilian.zinnecker--- via buildroot
2023-12-23 18:44 ` Yann E. MORIN
2024-01-08 11:06 ` Peter Korsgaard [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=87le90xexm.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=kilian.zinnecker@mail.de \
--cc=yann.morin.1998@free.fr \
/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