From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: yann.morin@orange.com
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] DEVELOPERS: add Yann E. MORIN (Orange) for docker credential helpers
Date: Fri, 31 Jul 2026 14:21:49 +0200 [thread overview]
Message-ID: <20260731122149.155363-1-thomas.perale@mind.be> (raw)
In-Reply-To: <7d8b63ec3a6f67c7935cfbda74cadcb5864d8cbe.1784100678.git.yann.morin@orange.com>
In reply of:
> Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Applied to 2026.05.x. Thanks
> ---
> DEVELOPERS | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/DEVELOPERS b/DEVELOPERS
> index 1601e6b408..42418d01a2 100644
> --- a/DEVELOPERS
> +++ b/DEVELOPERS
> @@ -3489,6 +3489,9 @@ F: package/tpm2-pkcs11/
>
> N: Yann E. MORIN <yann.morin@orange.com>
> F: .editorconfig
> +F: package/amazon-ecr-credential-helper/
> +F: package/docker-credential-acr-env/
> +F: package/docker-credential-gcr/
> F: package/gpsd/
> F: package/mosquitto/
> F: package/python-humanfriendly/
> --
> 2.34.1
>
> ____________________________________________________________________________________________________________
> 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
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-07-31 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 7:31 [Buildroot] [PATCH] DEVELOPERS: add Yann E. MORIN (Orange) for docker credential helpers yann.morin
2026-07-15 19:05 ` Julien Olivain via buildroot
2026-07-31 12:21 ` Thomas Perale via buildroot [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=20260731122149.155363-1-thomas.perale@mind.be \
--to=buildroot@buildroot.org \
--cc=thomas.perale@mind.be \
--cc=yann.morin@orange.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox