From: Peter Korsgaard <peter@korsgaard.com>
To: Scott Fan <fancp2007@gmail.com>
Cc: Bernd Kuhls <bernd@kuhls.net>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libopenssl: security bump version to 3.1.4
Date: Tue, 31 Oct 2023 13:34:33 +0100 [thread overview]
Message-ID: <87fs1r0y3q.fsf@48ers.dk> (raw)
In-Reply-To: <CAFkzVZbf3A4npP1DvXYkKo0dDTm_zxJMptdwR73J5EG3YpXH-w@mail.gmail.com> (Scott Fan's message of "Tue, 31 Oct 2023 19:08:46 +0800")
>>>>> "Scott" == Scott Fan <fancp2007@gmail.com> writes:
> Sorry, i thought it would always follow the upstream.
We normally do, but given that there is no added value for !windows, I
haven't done the work to update the LTS. Normally it would be taken care
of once the next update comes out with Linux fixes, but that is unlikely
to happen for 1.1.1 given that it is EOL.
But if you like to have 1.1.1w then that is fine by me, please send a
patch.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-10-31 13:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 18:19 [Buildroot] [PATCH 1/1] package/libopenssl: security bump version to 3.1.4 Bernd Kuhls
2023-10-29 8:45 ` Yann E. MORIN
2023-10-31 7:52 ` Peter Korsgaard
2023-10-31 9:00 ` Scott Fan
2023-10-31 9:48 ` Peter Korsgaard
2023-10-31 11:08 ` Scott Fan
2023-10-31 12:34 ` Peter Korsgaard [this message]
2023-11-01 1:58 ` [Buildroot] [PATCH] package/libopenssl: bump to version 1.1.1w Scott Fan
2023-11-07 16:50 ` Peter Korsgaard
2023-11-01 2:01 ` [Buildroot] [PATCH 1/1] package/libopenssl: security bump version to 3.1.4 Scott Fan
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=87fs1r0y3q.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=fancp2007@gmail.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