[FFmpeg-devel] Patch for Reproducing Issue 7827

mypopy at gmail.com mypopy at gmail.com
Thu Apr 4 12:28:19 EEST 2019


On Thu, Apr 4, 2019 at 3:12 PM Peter Belkner <pbelkner at snafu.de> wrote:
>
> On 04.04.2019 08:49, mypopy at gmail.com wrote:
>
> On Thu, Apr 4, 2019 at 2:33 PM Peter Belkner <pbelkner at snafu.de> wrote:
>
> This patch does not improve or fix something instead it is meant for
> easily reproducing issue 7827 (as requested, cf.
> https://trac.ffmpeg.org/ticket/7827). I've to admit that I don't know
> how to produce a patch by "git format-patch" instead it was made by "git
> diff > muxing.patch".
>
> A lot of docs for this type question, this is a refer
> https://www.x.org/wiki/Development/Documentation/SubmittingPatches/
>
> You can used the command like:
>
> git format-patch HEAD~1      # create a patch for the last commit
>
> And I think "git diff > muxing.patch"  will drop the commit message,
> it's a part of the patch for review, Tks.

>
> The patch produced with your command is attached. This is *not* the patch I want to provide.
>
> Just believe me: I'm able to search the internet myself and luckily finally found https://stackoverflow.com/questions/5159185/create-a-git-patch-from-the-changes-in-the-current-working-directory.
>
> BTW: I already spend hours to narrow this issue to libavformat. Just eat the provided patch either from the issue itself (cf. https://trac.ffmpeg.org/ticket/7827) or from this mailing list OR LET IT BE.
>
> Cheers.

Please try the patch https://patchwork.ffmpeg.org/patch/12612/, Thanks.


More information about the ffmpeg-devel mailing list