From: <Mikko.Rapeli@bmw.de>
To: <anuj.mittal@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] sqlite3: upgrade 3.30.1 -> 3.31.1
Date: Tue, 4 Feb 2020 09:21:26 +0000 [thread overview]
Message-ID: <20200204092125.GT104502@korppu> (raw)
In-Reply-To: <20200204055145.998317-1-anuj.mittal@intel.com>
Hi,
slightly off topic but I was checking CVEs for sqlite3 and noticed
this recipe uses the merged source tree format. This makes it very
hard to cherry-pick CVE and other patches from Debian, Ubuntu,
OpenSUSE etc.
Why use sqlite sources in "amalgamation" format?
https://sqlite.org/amalgamation.html
Cheers,
-Mikko
prev parent reply other threads:[~2020-02-04 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200204054432.822155-4-anuj.mittal@intel.com>
2020-02-04 5:51 ` [PATCH v2] sqlite3: upgrade 3.30.1 -> 3.31.1 Anuj Mittal
2020-02-04 9:21 ` Mikko.Rapeli [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=20200204092125.GT104502@korppu \
--to=mikko.rapeli@bmw.de \
--cc=anuj.mittal@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox