From: Rongqing Li <rongqing.li@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/6] subversion: backport 6 CVE patches
Date: Mon, 19 May 2014 09:53:24 +0800 [thread overview]
Message-ID: <53796414.1040503@windriver.com> (raw)
In-Reply-To: <CAJTo0Lb6euhg7DvXoFG62-tgASvPcJGRSHAu1GcHn9oXTHudkw@mail.gmail.com>
On 05/16/2014 06:39 PM, Burton, Ross wrote:
> On 16 May 2014 07:00, <rongqing.li@windriver.com> wrote:
>> subversion: fix for Security Advisory CVE-2013-1849
>> subversion: fix for Security Advisory CVE-2013-4505
>> subversion: fix for Security Advisory CVE-2013-4131
>> subversion: fix for Security Advisory CVE-2013-1845
>> subversion: fix for Security Advisory CVE-2013-1847 and CVE-2013-1846
>> subversion: fix for Security Advisory CVE-2013-4277
>
> Are these intended to be backported to daisy?
These patches can be cherry-picked to daisy, no need to modification.
-Roy
> For master, presumably
> we could upgrade to 1.7.16 or 1.8.9?
>
> Ross
>
>
--
Best Reagrds,
Roy | RongQing Li
next prev parent reply other threads:[~2014-05-19 1:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 6:00 [PATCH 0/6] subversion: backport 6 CVE patches rongqing.li
2014-05-16 6:00 ` [PATCH 1/6] subversion: fix for Security Advisory CVE-2013-1849 rongqing.li
2014-05-16 6:00 ` [PATCH 2/6] subversion: fix for Security Advisory CVE-2013-4505 rongqing.li
2014-05-16 6:00 ` [PATCH 3/6] subversion: fix for Security Advisory CVE-2013-4131 rongqing.li
2014-05-16 6:00 ` [PATCH 4/6] subversion: fix for Security Advisory CVE-2013-1845 rongqing.li
2014-05-16 6:00 ` [PATCH 5/6] subversion: fix for Security Advisory CVE-2013-1847 and CVE-2013-1846 rongqing.li
2014-05-16 6:00 ` [PATCH 6/6] subversion: fix for Security Advisory CVE-2013-4277 rongqing.li
2014-05-16 10:39 ` [PATCH 0/6] subversion: backport 6 CVE patches Burton, Ross
2014-05-19 1:53 ` Rongqing Li [this message]
2014-05-19 3:10 ` Saul Wold
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=53796414.1040503@windriver.com \
--to=rongqing.li@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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