From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: azxxza22 <amrtmoh2006@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] hash file added
Date: Fri, 7 Jan 2022 19:53:08 +0100 [thread overview]
Message-ID: <20220107195308.282518bc@windsurf> (raw)
In-Reply-To: <20220102181525.9494-2-amrtmoh2006@gmail.com>
Hello,
On Sun, 2 Jan 2022 20:15:25 +0200
azxxza22 <amrtmoh2006@gmail.com> wrote:
> Signed-off-by: azxxza22 <amrtmoh2006@gmail.com>
> ---
> package/nodogsplash/nodogsplash.hash | 2 ++
> 1 file changed, 2 insertions(+)
> create mode 100644 package/nodogsplash/nodogsplash.hash
This should be part of the patch adding the package.
> diff --git a/package/nodogsplash/nodogsplash.hash b/package/nodogsplash/nodogsplash.hash
> new file mode 100644
> index 0000000000..da059a854d
> --- /dev/null
> +++ b/package/nodogsplash/nodogsplash.hash
> @@ -0,0 +1,2 @@
> +md5 edafdd4ef89218261f29a9074891cf7a nodogsplash-v4.5.1-br1.tar.gz
> +md5 cbbd794e2a0a289b9dfcc9f513d1996e COPYING
These should be sha256 hashes, and there should be a comment above that
says:
# Locally calculated
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-07 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 18:15 [Buildroot] [PATCH 1/2] nodogsplash package added azxxza22
2022-01-02 18:15 ` [Buildroot] [PATCH 2/2] hash file added azxxza22
2022-01-07 18:53 ` Thomas Petazzoni [this message]
2022-01-07 18:51 ` [Buildroot] [PATCH 1/2] nodogsplash package added Thomas Petazzoni
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=20220107195308.282518bc@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=amrtmoh2006@gmail.com \
--cc=buildroot@buildroot.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 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.