On 03/16/2016 09:17 AM, Mats Peterson wrote:
On 03/16/2016 09:12 AM, Hendrik Leppkes wrote:
On Wed, Mar 16, 2016 at 9:07 AM, Mats Peterson
<matsp888-at-yahoo....@ffmpeg.org> wrote:
On 03/16/2016 09:07 AM, Hendrik Leppkes wrote:
On Wed, Mar 16, 2016 at 9:03 AM, Mats Peterson
<matsp888-at-yahoo....@ffmpeg.org> wrote:
On 03/16/2016 09:04 AM, Hendrik Leppkes wrote:
On Wed, Mar 16, 2016 at 8:59 AM, Mats Peterson
<matsp888-at-yahoo....@ffmpeg.org> wrote:
On 03/16/2016 08:55 AM, Hendrik Leppkes wrote:
On Wed, Mar 16, 2016 at 7:50 AM, Mats Peterson
<matsp888-at-yahoo....@ffmpeg.org> wrote:
On 03/16/2016 04:48 AM, Mats Peterson wrote:
On 03/16/2016 04:45 AM, Mats Peterson wrote:
You say the libav commits are merged every day. This commit was
posted
February 22, that's quite a while ago. What is it that causes
this
delay?
Mats
This is a super-simple patch, at that.
Mats
Once again, couldn't I just make a new patch with the relevant
changes
to
libavcodec/indeo2.c and libavcodec/indeo2data.h, and attribute
Luca
Barbato
in some way?
Either you cherry-pick it properly, or you don't do it at all. So
apparently, no, you cannot.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
We'll see what Michael says about that.
He already said this in an earlier mail, and you ignored him all the
same. You should try to listen to people and not just do wtf you
want.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
I don't know how the fsck to use that cherry-pick crap.
Then figure it out, or wait until someone merges it. Manually messing
with these things just makes more work for everyone else, which is why
we don't accept it. Its as simple as that.
_______________________________________________
ffmpeg-devel mailing list
Then why hasn't it been merged yet? You said yourself libav commits are
merged "every day", unless there is some obstacle. What could this
obstacle
be this time? The commit was posted February 22. It's a fairly long
time.
There is a few complex API changes before them which take careful work
to merge without breaking them, it just takes a bit of time.
PS:
The commit in question was pushed on March 1, not in February.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
In any case, I don't see anything wrong with creating a patch that
includes those changes, as long as I attribute the author properly. It's
no different from writing it myself, once again.
Mats
What Michael said no to was *copying* the files, and that's fully
understandable, since they contain references to Libav at the top.
Mats
--
Mats Peterson
http://matsp888.no-ip.org/~mats/
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
