On 11/04/2018 00:16, Lou Logan wrote:
On Tue, Apr 10, 2018, at 2:05 PM, Michael Niedermayer wrote:
what do you mean by "Git and me are not good friends" ?
If git hates you and sometimes does things that you didnt intend at all then
that would be a problem with direct pushes as theres no way to undo.
But maybe i misunderstand.
Yes, that's right :), I think you also remarked that I am an expert of
careless mistakes :(.
I am still at the bottom of the Git learning curve, being more used to
the GitHub PR things (which IMO avoids well to do a mess with upstream
Additionally, I think that it does not worth it to take risks (including
the risk of compromised machine) about giving me write rights with the
only few patches I send. It would be another story if I become more
active on FFmpeg code in the future.
Also to get git write access, post a patch that adds yourself to the
MAINTAINERs file. When noone objects then ill add your key and apply
the MAINTAINER patch.
Also, if you're uncomfortable pushing to the repository that's fine too. It is
not a problem, but you may have to prod and remind us, perhaps a few times (or
more), to push stuff.
I kindly request a maintainer to push one (the latest one?) of the DPX
patches in this thread (i.e. right I am uncomfortable pushing to FFmpeg
repo directly, I would do it only if it is the only method for having my
patches pushed upstream after review due to no current maintainer
willing to push them), as well as reviewing then push (if they are fine)
the ones related to FFV1 
ffmpeg-devel mailing list