[FFmpeg-devel] [PATCH 1/4] add a generic function to lavc to log messages about missing features.

Måns Rullgård mans
Sun Jul 20 10:47:36 CEST 2008


Alexander Strange <astrange at ithinksw.com> writes:

> On Jul 19, 2008, at 8:31 PM, Justin Ruggles wrote:
>
>> Michael Niedermayer wrote:
>>> On Sat, Jul 19, 2008 at 07:50:25PM -0400, justin.ruggles at gmail.com  
>>> wrote:
>>>> ---
>>>> libavcodec/avcodec.h |   11 +++++++++++
>>>> libavcodec/utils.c   |   12 ++++++++++++
>>>> 2 files changed, 23 insertions(+), 0 deletions(-)
>>>> diff --git a/libavcodec/avcodec.h b/libavcodec/avcodec.h
>>>> index 4942ab1..33a1258 100644
>>>
>>> It would be very nice if you could get your git-send-mail to  
>>> include the
>>> commit message in the mail. (this applies to other people as well)
>>
>> I haven't been able to do this, but I'll keep trying.  If I can't  
>> figure
>> it out before I need to send another patch set, I'll manually edit the
>> patches before using git-send-email.
>
> I think M?ns said that adding another blank line after the subject in  
> the patch file worked for him. You can do that either when writing  
> commit messages or by editing the patch by hand.

git-format-patch uses the first line of the comment as email subject,
and includes anything following the first blank line in the message
body.

> I'm not sure but it might need one trailing space instead of just a  
> blank line.

No, git hates trailing whitespace just as much as we do.

-- 
M?ns Rullg?rd
mans at mansr.com




More information about the ffmpeg-devel mailing list