All of lore.kernel.org
 help / color / mirror / Atom feed
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 00/16 v2] merge 16 CVE patches
Date: Wed, 23 Jul 2014 09:32:18 +0800	[thread overview]
Message-ID: <53CF10A2.7000402@windriver.com> (raw)
In-Reply-To: <CAJTo0LZCtnBuZrWBuBmxdO8Z5SYRFbO1tYR2_GUCp4TNet9Ugg@mail.gmail.com>



On 07/22/2014 04:22 PM, Burton, Ross wrote:
> On 22 July 2014 08:46,  <rongqing.li@windriver.com> wrote:
>> Yue Tao (16):
>>    gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-0866
>>    gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-0875
>>    gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-0860
>>    gst-ffmpeg: Security Advisory - ffmpeg - CVE-2011-3934
>>    gst-ffmpeg: Security Advisory - ffmpeg - CVE-2011-3946
>>    gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-7023
>>    gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-7009
>>    gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-0855
>>    gst-ffmpeg: Security Advisory - ffmpeg - CVE-2011-4351
>>    gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-0848
>>    gst-ffmpeg: Security Advisory - ffmpeg - CVE-2011-3944
>>    gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-7010
>>    gst-ffmpeg: Security Advisory - ffmpeg - CVE-2011-3941
>>    gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-0846
>>    gst-ffmpeg: Security Advisory - ffmpeg - CVE-2012-6618
>>    gst-ffmpeg: Security Advisory - ffmpeg - CVE-2012-6617
>
> As there's no benefit in being able to bisect this, I think it would
> be neater if these were squashed into a single commit.
>

I am fine, Saul can squash them when merge

-Roy

> Ross
>
>

-- 
Best Reagrds,
Roy | RongQing Li


      reply	other threads:[~2014-07-23  1:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22  7:46 [PATCH 00/16 v2] merge 16 CVE patches rongqing.li
2014-07-22  7:46 ` [PATCH 01/16] gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-0866 rongqing.li
2014-07-22  7:46 ` [PATCH 02/16] gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-0875 rongqing.li
2014-07-22  7:46 ` [PATCH 03/16] gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-0860 rongqing.li
2014-07-22  7:46 ` [PATCH 04/16] gst-ffmpeg: Security Advisory - ffmpeg - CVE-2011-3934 rongqing.li
2014-07-22  7:46 ` [PATCH 05/16] gst-ffmpeg: Security Advisory - ffmpeg - CVE-2011-3946 rongqing.li
2014-07-22  7:46 ` [PATCH 06/16] gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-7023 rongqing.li
2014-07-22  7:46 ` [PATCH 07/16] gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-7009 rongqing.li
2014-07-22  7:46 ` [PATCH 08/16] gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-0855 rongqing.li
2014-07-22  7:46 ` [PATCH 09/16] gst-ffmpeg: Security Advisory - ffmpeg - CVE-2011-4351 rongqing.li
2014-07-22  7:46 ` [PATCH 10/16] gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-0848 rongqing.li
2014-07-22  7:46 ` [PATCH 11/16] gst-ffmpeg: Security Advisory - ffmpeg - CVE-2011-3944 rongqing.li
2014-07-22  7:46 ` [PATCH 12/16] gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-7010 rongqing.li
2014-07-22  7:46 ` [PATCH 13/16] gst-ffmpeg: Security Advisory - ffmpeg - CVE-2011-3941 rongqing.li
2014-07-22  7:46 ` [PATCH 14/16] gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-0846 rongqing.li
2014-07-22  7:46 ` [PATCH 15/16] gst-ffmpeg: Security Advisory - ffmpeg - CVE-2012-6618 rongqing.li
2014-07-22  7:46 ` [PATCH 16/16] gst-ffmpeg: Security Advisory - ffmpeg - CVE-2012-6617 rongqing.li
2014-07-22  8:22 ` [PATCH 00/16 v2] merge 16 CVE patches Burton, Ross
2014-07-23  1:32   ` Rongqing Li [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=53CF10A2.7000402@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 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.