From: "Pawan Badganchi" <badganchipv@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [meta][dunfell][PATCH 2/2] curl: Add fix for CVE-2023-23916
Date: Fri, 24 Mar 2023 01:00:41 -0700 [thread overview]
Message-ID: <4110.1679644841958673904@lists.openembedded.org> (raw)
In-Reply-To: <20230324075526.22055-2-badganchipv@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 27 bytes --]
Please ignore this patch.
[-- Attachment #2: Type: text/html, Size: 27 bytes --]
next prev parent reply other threads:[~2023-03-24 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 7:55 [meta][dunfell][PATCH 1/2] curl: Add fix for CVE-2023-23914, CVE-2023-23915 pawan
2023-03-24 7:55 ` [meta][dunfell][PATCH 2/2] curl: Add fix for CVE-2023-23916 pawan
2023-03-24 8:00 ` Pawan Badganchi [this message]
2023-03-24 8:01 ` [meta][dunfell][PATCH 1/2] curl: Add fix for CVE-2023-23914, CVE-2023-23915 Pawan Badganchi
2023-03-24 15:43 ` [OE-core] " Steve Sakoman
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=4110.1679644841958673904@lists.openembedded.org \
--to=badganchipv@gmail.com \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.