From: <yann.morin@orange.com>
To: <buildroot@buildroot.org>
Cc: "Yann E . MORIN" <yann.morin@orange.com>
Subject: [Buildroot] [PATCH 0/3] package: add hashes to license files for docker credential helpers
Date: Fri, 13 Jun 2025 07:44:41 +0200 [thread overview]
Message-ID: <cover.1749793479.git.yann.morin@orange.com> (raw)
From: "Yann E. MORIN" <yann.morin@orange.com>
Hello All!
The various recently introduced packages that provide Docker credential
helpers, did not have a hash for their license files.
This series adds such hashes now.
Regards,
Yann E. MORIN.
The following changes since commit d02a1239a553f31605e63b0fb50d9ea4e5e0d987
package/linux-headers: drop 6.14.x option (2025-06-12 22:54:20 +0200)
are available as patches in this mail series,
for you to apply patches up to d2a08a5ea591122a0a08567e98a89ef0a26cc21a
package/docker-credential-gcr: add LICENSE hash (2025-06-13 07:42:31 +0200)
----------------------------------------------------------------
Yann E. MORIN (3):
package/amazon-ecr-credential-helper: add LICENSE hash
package/docker-credential-acr-env: add LICENSE hash
package/docker-credential-gcr: add LICENSE hash
package/amazon-ecr-credential-helper/amazon-ecr-credential-helper.hash | 1 +
package/docker-credential-acr-env/docker-credential-acr-env.hash | 1 +
package/docker-credential-gcr/docker-credential-gcr.hash | 1 +
3 files changed, 3 insertions(+)
--
____________
.-----------------.--------------------: _ :------------------.
| Yann E. MORIN | Real-Time Embedded | __/ ) | /"\ ASCII RIBBON |
| | Software Designer | _/ - /' | \ / CAMPAIGN |
| +33 638.411.245 '--------------------: (_ `--, | X AGAINST |
| yann.morin (at) orange.com |_=" ,--' | / \ HTML MAIL |
'--------------------------------------:______/_____:------------------'
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2025-06-13 5:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 5:44 yann.morin [this message]
2025-06-13 5:44 ` [Buildroot] [PATCH 1/3] package/amazon-ecr-credential-helper: add LICENSE hash yann.morin
2025-06-13 21:39 ` Julien Olivain
2025-06-26 19:52 ` Thomas Perale via buildroot
2025-06-13 5:44 ` [Buildroot] [PATCH 2/3] package/docker-credential-acr-env: " yann.morin
2025-06-13 5:44 ` [Buildroot] [PATCH 3/3] package/docker-credential-gcr: " yann.morin
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=cover.1749793479.git.yann.morin@orange.com \
--to=yann.morin@orange.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox