All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Andrei Gherzan <andrei@gherzan.ro>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 2/2] libav: Update to v0.8.8
Date: Wed, 04 Dec 2013 18:33:40 +0000	[thread overview]
Message-ID: <17330076.MJ53DVLGsZ@helios> (raw)
In-Reply-To: <1386180088-27454-2-git-send-email-andrei@gherzan.ro>

Hi Andrei,

On Wednesday 04 December 2013 20:01:28 Andrei Gherzan wrote:
> Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
> ---
>  .../0001-configure-enable-pic-for-AArch64.patch    | 23
> ---------------------- .../0001-configure-enable-pic-for-AArch64.patch    |
> 23 ++++++++++++++++++++++ meta/recipes-multimedia/libav/libav_0.8.8.bb     
>  | 18 ----------------- meta/recipes-multimedia/libav/libav_0.8.9.bb      
> | 16 +++++++++++++++ 4 files changed, 39 insertions(+), 41 deletions(-)
>  delete mode 100644
> meta/recipes-multimedia/libav/libav-0.8.8/0001-configure-enable-pic-for-AAr
> ch64.patch create mode 100644
> meta/recipes-multimedia/libav/libav-0.8.9/0001-configure-enable-pic-for-AAr
> ch64.patch delete mode 100644 meta/recipes-multimedia/libav/libav_0.8.8.bb
>  create mode 100644 meta/recipes-multimedia/libav/libav_0.8.9.bb

Thanks, but a few things:

1) The shortlog says 0.8.8, but this is upgrading to 0.8.9

2) Please use -M so we can see the changes

3) These patches need to be sent to the OE-Core list instead

FWIW, I actually had this update queued already, but I hadn't sent it yet 
because I hadn't tested it beyond building it - did you test this at runtime?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-12-04 18:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04 18:01 [PATCH 1/2] libav: Add v9.10 Andrei Gherzan
2013-12-04 18:01 ` [PATCH 2/2] libav: Update to v0.8.8 Andrei Gherzan
2013-12-04 18:33   ` Paul Eggleton [this message]
2013-12-04 18:40   ` Martin Jansa
2013-12-04 18:48     ` Andrei Gherzan

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=17330076.MJ53DVLGsZ@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=andrei@gherzan.ro \
    --cc=yocto@yoctoproject.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.