[FFmpeg-devel] [PATCH] ffserver regression jpg fix for mjpg streaming data sent to browser instead of jpg image

[ill]

>> That file is attached
>>> you would have to attach the file generated by git format-patch
>>> also you of course first need to locally commit your changes
>>> and set the commit message and author
>>> see man git commit
>>>
>>> [...]
>>>
>>>
>>>
>>> _______________________________________________
>>> ffmpeg-devel mailing list
>>> ffmpeg-devel at ffmpeg.org
>>> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>>
>>
>>
>>
>>
>>
>>   ffserver.c               |    4 ++++
>>   ffserver_config.c        |    6 ++++--
>>   ffserver_config.h        |    1 +
>>   libavformat/allformats.c |    1 +
>>   libavformat/rawenc.c     |   12 ++++++++++++
>>   5 files changed, 22 insertions(+), 2 deletions(-)
>> 45033f4565049ec4b1893023d52ce1799610a902  0001-ffserver-jpg-patch.patch
>>  From 5b681fdaf7971f841b84cfe06412c67ba417fb00 Mon Sep 17 00:00:00 2001
>> From: Caligula useraccount <caligula at sarijopen.student.utwente.nl>
>> Date: Mon, 11 May 2015 17:42:42 -0600
>> Subject: [PATCH] ffserver jpg patch
> the commit message should describe what the commit does
> how it does it and why it does
>

It fixes a regression that ffserver doesn't use jpg for said format.

>> ---
>>   ffserver.c               |  4 ++++
>>   ffserver_config.c        |  6 ++++--
>>   ffserver_config.h        |  1 +
>>   libavformat/allformats.c |  1 +
>>   libavformat/rawenc.c     | 12 ++++++++++++
> changes to libavformat and ffserver should be in seperate patches
> ideally
Do you have experience in that? I tried cutting and pasting the 
libavformat parts to a different patch but that makes it not work. Is 
that a strict requirement? I think the changes don't work separately.

> also please see
> http://ffmpeg.org/developer.html#New-codecs-or-formats-checklist
It's not a new codec or format. All it does is fix an already existing 
format (jpg)
I also don't know what 90% of the stuff it is talking about on that page 
is, but it does compile and fixes the bug, so 12 is good, and I think 4.

> Thanks
>
> [...]
>
>
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel