[FFmpeg-devel] [PATCH] avutil/parseutils: add av_warn_unused_result
gajjanag at mit.edu
Fri Oct 16 04:24:01 CEST 2015
On Thu, Oct 15, 2015 at 10:22 PM, Ganesh Ajjanagadde <gajjanag at mit.edu> wrote:
> On Thu, Oct 15, 2015 at 10:16 PM, James Almer <jamrial at gmail.com> wrote:
>> On 10/15/2015 10:23 PM, Ganesh Ajjanagadde wrote:
>>> On Thu, Oct 15, 2015 at 8:06 PM, James Almer <jamrial at gmail.com> wrote:
>>>> On 10/15/2015 8:52 PM, Ganesh Ajjanagadde wrote:
>>>>> This triggers a few warnings that will need to be fixed - not that bad,
>>>>> the current code is mostly fine.
>>>> I think i asked you before, but in any case i'll do it again. Please,
>>>> send patchsets contained in a single thread. You're making things
>>>> hard to track and organize on people's inboxes.
>>>> See https://kernel.org/pub/software/scm/git/docs/git-send-email.html
>>>> --thread, --chain-reply-to and --in-reply-to options.
>>> Would greatly appreciate a command/command sequence: I am on master
>>> (which is ahead of origin/master) and contains only the avutil warning
>>> stuff (many commits). How do I get a proper chain of emails that you
>>> would like?
>> When you send several mails with a single git send-email command, it
>> should by default send every email after the first as a reply to the
>> first, effectively making a single "thread".
> Sorry, but gmail smtp/send-email does not let me do this - I have
> tried multiple patches in a single git send-email, and it closes the
The engineers at Google must have fixed something - I tried it just
now in the manner you described for the avdevice patches.
>> When you send one email at a time, you'll have to use --in-reply-to
>> as part of the git send-email command, using the message ID of the email
>> you want as parent as argument.
>> ffmpeg-devel mailing list
>> ffmpeg-devel at ffmpeg.org
More information about the ffmpeg-devel