From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: rongqing.li@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH][V2] sqlite3: upgrade to 3.8.10
Date: Tue, 19 May 2015 11:50:13 +0100 [thread overview]
Message-ID: <1432032613.32616.26.camel@linuxfoundation.org> (raw)
In-Reply-To: <1432016139-20019-1-git-send-email-rongqing.li@windriver.com>
On Tue, 2015-05-19 at 14:15 +0800, rongqing.li@windriver.com wrote:
> From: Roy Li <rongqing.li@windriver.com>
>
> upgrade to include CVE fixes
No mention of the additional patch?
>
> Signed-off-by: Roy Li <rongqing.li@windriver.com>
> ---
> .../files/0001-using-the-dynamic-library.patch | 28 ++++++++++++++++++++++
> .../{sqlite3_3.8.7.4.bb => sqlite3_3.8.10.0.bb} | 8 ++++---
> 2 files changed, 33 insertions(+), 3 deletions(-)
> create mode 100644 meta/recipes-support/sqlite/files/0001-using-the-dynamic-library.patch
> rename meta/recipes-support/sqlite/{sqlite3_3.8.7.4.bb => sqlite3_3.8.10.0.bb} (64%)
>
> diff --git a/meta/recipes-support/sqlite/files/0001-using-the-dynamic-library.patch b/meta/recipes-support/sqlite/files/0001-using-the-dynamic-library.patch
> new file mode 100644
> index 0000000..5818aa2
> --- /dev/null
> +++ b/meta/recipes-support/sqlite/files/0001-using-the-dynamic-library.patch
> @@ -0,0 +1,28 @@
> +[PATCH] using the dynamic library
> +
> +Upstream-Status: Inappropriate [configuration]
> +
> +using the dynamic library, not link statically
This says what you've done but not why? Why do we need to do this?
Cheers,
Richard
prev parent reply other threads:[~2015-05-19 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 6:15 [PATCH][V2] sqlite3: upgrade to 3.8.10 rongqing.li
2015-05-19 10:50 ` Richard Purdie [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=1432032613.32616.26.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rongqing.li@windriver.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 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.