Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ffmpeg: bump to 0.11.1
Date: Sun, 17 Jun 2012 11:09:43 +0200	[thread overview]
Message-ID: <871ulegv8o.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4FDB2E46.8090705@elvees.com> (Anton Leontiev's message of "Fri,  15 Jun 2012 16:44:54 +0400")

>>>>> "Anton" == Anton Leontiev <aleontiev@elvees.com> writes:

 Anton> Signed-off-by: Anton Leontiev <aleontiev@elvees.com>

Thanks, but I cannot commit it as it is now. First of all, Thunderbird
had corrupted your patch by word wrapping and stripping trailing
spaces. Please use git send-email and/or test patches by sending them to
yourself and see if they still applies for next time.

Secondly, we have a number of other packages using ffmpeg, and the 0.11
version seems to change the APi in a number of ways. From a quick build
test I see that:

- gst-ffmpeg
- mediastreamer
- opencv

Are broken, so those packages would need to be upgraded / fixed before.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2012-06-17  9:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 12:44 [Buildroot] [PATCH] ffmpeg: bump to 0.11.1 Anton Leontiev
2012-06-17  9:09 ` Peter Korsgaard [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=871ulegv8o.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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