[FFmpeg-devel] [PATCH 2/4] dxva2: use a single macro to test if the DXVA context is valid

[Steve Lhomme]

On Fri, Jan 13, 2017 at 1:04 PM, Michael Niedermayer <michaelni at gmx.at> wrote:
> On Fri, Jan 13, 2017 at 01:01:14PM +0100, Michael Niedermayer wrote:
>> On Fri, Jan 13, 2017 at 10:40:23AM +0000, Stève Lhomme wrote:
>> > On Fri, Jan 13, 2017 at 10:47 AM, wm4 <nfxjfg at googlemail.com> wrote:
>> > > On Fri, 13 Jan 2017 09:52:18 +0100
>> > > Steve Lhomme <robux4 at gmail.com> wrote:
>> > >
>> > >> For the record all 3 remaining patches (2/4, 3/4 and 4/4) are now
>> > >> merged in libav.
>> > >
>> > > So how do we handle this. Do we wait until the merges catch up, or do
>> > > you want to push your patches to ffmpeg's git immediately?
>> >
>> > Not sure what you mean. What merge are you talking about ?
>> > These 3 patches can live on their own, regardless of what is being
>> > done with d3d11va in hwcontext and ffmpeg.
>> > I can send again 4/4 as the version number needs to be updated.
>>
>> when resending you may want to add a patch to add yourself to the
>> MAINTAINERs file, maybe for d3d11va or any other part you want
>
> to clarify, i think you should have write access to git and the

OK, How does commit work ? login/pass via HTTP ? ssh key ?

> list of people havig write access should match the list of people in
> MAINTAINERs

I've sent the updated patches and added myself for DXVA2 and D3D11VA stuff.

> [...]
>
> --
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> During times of universal deceit, telling the truth becomes a
> revolutionary act. -- George Orwell
>
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>