From: Peter Korsgaard <peter@korsgaard.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Asaf Kahlon <asafka7@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python-requests: bump to version 2.31.0
Date: Mon, 19 Jun 2023 17:25:21 +0200 [thread overview]
Message-ID: <87mt0vpj8e.fsf@48ers.dk> (raw)
In-Reply-To: <20230605073324.1889371-1-james.hilliard1@gmail.com> (James Hilliard's message of "Mon, 5 Jun 2023 01:33:24 -0600")
>>>>> "James" == James Hilliard <james.hilliard1@gmail.com> writes:
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
This should ideally have been marked as a security bump:
https://github.com/psf/requests/security/advisories/GHSA-j8r2-6x86-q33q
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-06-19 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 7:33 [Buildroot] [PATCH 1/1] package/python-requests: bump to version 2.31.0 James Hilliard
2023-06-18 13:09 ` Arnout Vandecappelle via buildroot
2023-06-19 15:25 ` Peter Korsgaard [this message]
2023-07-06 11:42 ` Peter Korsgaard
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=87mt0vpj8e.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=asafka7@gmail.com \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@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