[FFmpeg-devel] [PATCH 1/6] lavc/aarch64: new optimization for 8-bit hevc_pel_bi_pixels

Logan.Lyu Logan.Lyu at myais.com.cn
Fri Nov 24 14:19:18 EET 2023


Hi, Martin,

This is indeed a weird mistake... I don't know how to fixed it...

And  can you try those .patch files I attached in every email?  I 
downloaded the attachment from the ffmpeg-devel mailing list I 
subscribed to and applied it, and it seems to work.

If the method mentioned above still doesn't work, should I re-send the 
.eml files one by one?  Please tell me how to deal with it, I will be 
grateful.

Thanks


在 2023/11/22 20:36, Martin Storsjö via ffmpeg-devel 写道:
> On Wed, 22 Nov 2023, Logan.Lyu wrote:
>
>> I can't reproduce the error you mentioned...
>>
>> I can apply patches to the ffmpeg master branch normally using 'git 
>> apply xxx.patch/.eml' or 'git am xxx.patch/.eml'.
>
> I guess you have emails that haven't been through the complete 
> delivery chain, while some later party might have rewritten things.
>
>> By the way, I create these patches by /'git format-patch -s -o "../" 
>> --add-header "X-Unsent: 1" --suffix .eml --to ffmpeg-devel at ffmpeg.org 
>> -6 --filename-max-length=100' /to generate .eml file.  And /'git 
>> format-patch  -4 --filename-max-length=100' /to generate .patch file 
>> as attachment to prevent encoding format problems in email files. 
>> These command should be OK, right?
>
> That's right for generating the patch files. I guess the problem here 
> isn't about the patch files themselves, but the email delivery of them.
>
>> Can you try these patches again? If the error still occurs, please 
>> tell me how it occurred then I will fixed it.
>
> I also tried applying them now with "git am", and I got this:
>
> Applying: lavc/aarch64: new optimization for 8-bit hevc_pel_bi_pixels
> error: corrupt patch at line 194
> Patch failed at 0001 lavc/aarch64: new optimization for 8-bit 
> hevc_pel_bi_pixels
> hint: Use 'git am --show-current-patch=diff' to see the failed patch
>
> Thus, same issue here.
>
> In earlier iterations, the patches have arrived correctly when you 
> have sent them as attachments, instead of when sending them as plain 
> inline patches with git send-email.
>
> // Martin
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".


More information about the ffmpeg-devel mailing list