From: hung kuishing <hungkuishing@outlook.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] doc/examples/qsv_decode.c: remove unused config.h header file
Date: Mon, 11 Mar 2024 13:41:43 +0000
Message-ID: <PH7PR11MB74304A92AA1363C774BF46B4C4242@PH7PR11MB7430.namprd11.prod.outlook.com> (raw)
In-Reply-To: <Ze27xf2TxJcPS05Q@mariano>
> 在 2024年3月10日，21:55，Stefano Sabatini <stefasab@gmail.com> 写道：
>
> On date Saturday 2024-03-09 02:17:19 +0000, hung kuishing wrote:
>>
>> Signed-off-by: clarkh <hungkuishing@outlook.com<mailto:hungkuishing@outlook.com>>
>> ---
>> doc/examples/qsv_decode.c | 2 --
>> 1 file changed, 2 deletions(-)
>>
>> diff --git a/doc/examples/qsv_decode.c b/doc/examples/qsv_decode.c
>> index cc2662d5bd..901eac3b27 100644
>> --- a/doc/examples/qsv_decode.c
>> +++ b/doc/examples/qsv_decode.c
>> @@ -28,8 +28,6 @@
>> * GPU video surfaces, write the decoded frames to an output file.
>> */
>>
>> -#include "config.h"
>> -
>> #include <stdio.h>
>>
>> #include "libavformat/avformat.h"
>> --
>> 2.34.1
>
> Looks good but it fails with:
> git am --abort; git am patches/fix-doc-qsvdec.patch
> Applying: doc/examples/qsv_decode.c: remove unused config.h header file
> error: corrupt patch at line 15
>
> Can you try to generate the patch (git format-patch) and attach it to
> the thread?
>
> Or I'll just apply the diff manually.
Ok, please apply the diff manually, thanks
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-03-11 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 2:17 hung kuishing
2024-03-10 13:55 ` Stefano Sabatini
2024-03-11 13:41 ` hung kuishing [this message]
2024-03-12 10:18 ` Stefano Sabatini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PH7PR11MB74304A92AA1363C774BF46B4C4242@PH7PR11MB7430.namprd11.prod.outlook.com \
--to=hungkuishing@outlook.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git