Re: [FFmpeg-devel] release/3.1

2016-06-30 Thread Amancio Hasty
How is this commit then for ticket #3518: e330ab0fb7cb140cfde98077e1a953c200282087 Merge: 0e38723 f1cd9b0 Author: Derek Buitenhuis Date: Wed May 11 19:23:15 2016 +0100 Merge commit 'f1cd9b03f3fa875eb5e394281b4b688cec611658' * commit 'f1cd9b03f3fa875eb5e394281b4b688cec611658': om

Re: [FFmpeg-devel] release/3.1

2016-06-27 Thread Amancio Hasty
This is the commit that introduced the functionality: f1cd9b03f3fa875eb5e394281b4b688cec611658 Amancio On June 27, 2016 at 5:35:33 AM, Carl Eugen Hoyos (ceho...@ag.or.at) wrote: Amancio Hasty gmail.com> writes: > You can close ticket #3518 which states that ffmpeg does not > support RPI’s

Re: [FFmpeg-devel] release/3.1

2016-06-27 Thread Carl Eugen Hoyos
Amancio Hasty gmail.com> writes: > You can close ticket #3518 which states that ffmpeg does not > support RPI’s hardware h264 encoding. Which commit fixed #3518? Thank you, Carl Eugen ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpe

Re: [FFmpeg-devel] release/3.1

2016-06-27 Thread Amancio Hasty
On June 26, 2016 at 5:49:30 PM, Michael Niedermayer (mich...@niedermayer.cc) wrote: On Sun, Jun 26, 2016 at 03:36:33AM +0200, Michael Niedermayer wrote: > Hi all > > ive branched release/3.1 off from master > i will make the 3.1 release from HEAD of this branch tomorrow > If there are any last min

Re: [FFmpeg-devel] release/3.1

2016-06-27 Thread Thomas Volkert
On 27.06.2016 02:48, Michael Niedermayer wrote: > On Sun, Jun 26, 2016 at 03:36:33AM +0200, Michael Niedermayer wrote: >> Hi all >> >> ive branched release/3.1 off from master >> i will make the 3.1 release from HEAD of this branch tomorrow >> If there are any last minute changes that should go in,

Re: [FFmpeg-devel] release/3.1

2016-06-26 Thread Michael Niedermayer
On Sun, Jun 26, 2016 at 03:36:33AM +0200, Michael Niedermayer wrote: > Hi all > > ive branched release/3.1 off from master > i will make the 3.1 release from HEAD of this branch tomorrow > If there are any last minute changes that should go in, thats your > very last chance to put them in ! 3.1 r