From: Peter Korsgaard <peter@korsgaard.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/6 v2] utils/check-package: use https for the manual URL
Date: Sat, 09 Mar 2024 14:36:07 +0100 [thread overview]
Message-ID: <874jdfv86w.fsf@48ers.dk> (raw)
In-Reply-To: <d4690e555ad7f84c9340bc66d7bc0a75edcbbf46.1707600292.git.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Sat, 10 Feb 2024 22:24:54 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Committed to 2023.02.x and 2023.11.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-03-09 13:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 21:24 [Buildroot] [PATCH 0/6 v2] utils/checkpackagelib: check CPE variables (branch yem/checkpkg-cpe) Yann E. MORIN
2024-02-10 21:24 ` [Buildroot] [PATCH 1/6 v2] utils/check-package: use https for the manual URL Yann E. MORIN
2024-03-09 13:36 ` Peter Korsgaard [this message]
2024-02-10 21:24 ` [Buildroot] [PATCH 2/6 v2] doc/manual: fixup ordered lists Yann E. MORIN
2024-03-09 13:37 ` Peter Korsgaard
2024-02-10 21:24 ` [Buildroot] [PATCH 3/6 v2] doc/manual: indent the CVE example the same as the CVE list item Yann E. MORIN
2024-03-09 13:37 ` Peter Korsgaard
2024-02-10 21:24 ` [Buildroot] [PATCH 4/6 v2] doc/manual: document _CPE_ID_VALID Yann E. MORIN
2024-02-10 21:24 ` [Buildroot] [PATCH 5/6 v2] package: switch to _CPE_ID_VALID Yann E. MORIN
2024-02-10 21:24 ` [Buildroot] [PATCH 6/6 v2] utils/checkpackagelib: add check for CPE variables set to default values Yann E. MORIN
2024-02-11 15:31 ` [Buildroot] [PATCH 0/6 v2] utils/checkpackagelib: check CPE variables (branch yem/checkpkg-cpe) Thomas Petazzoni via buildroot
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=874jdfv86w.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--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