From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] Long path support for Windows (fixes #8885)
Date: Mon, 14 Feb 2022 09:49:46 +0530
Message-ID: <bd8de547-e40b-9d34-d283-a762adea2e4c@gyani.pro> (raw)
In-Reply-To: <Mvol-q3--3-2@tutanota.com>
On 2022-02-14 01:56 am, nihil-admirari@tutanota.com wrote:
> BASE64 encoded.
Rebase against current HEAD and submit via git send-email.
If not possible, export mbox patch using git format-patch,
test with git am locally. Then send as attachment.
Regards,
Gyan
>
> Feb 13, 2022, 19:54 by nihil-admirari@tutanota.com:
>
>> Let's try once again with .txt
>>
>> Feb 13, 2022, 19:52 by nihil-admirari@tutanota.com:
>>
>>> Let's try once again with .diff extension.
>>>
>>> Feb 13, 2022, 19:48 by nihil-admirari@tutanota.com:
>>>
>>>> Previous patch got corrupted with lots of unbreakable spaces C2 A0, so it does not apply: >>> https://patchwork.ffmpeg.org/project/ffmpeg/patch/Mvn2TLP--3-2@tutanota.com/>>> . Let's retry with an attachment.
>>> >
>>>
>>> _______________________________________________
>>> 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".
_______________________________________________
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".
prev parent reply other threads:[~2022-02-14 4:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 12:28 nihil-admirari
2022-02-13 14:25 ` Timo Rothenpieler
2022-02-13 14:33 ` nihil-admirari
2022-02-13 19:48 ` nihil-admirari
2022-02-13 19:52 ` nihil-admirari
2022-02-13 19:54 ` nihil-admirari
2022-02-13 20:26 ` nihil-admirari
2022-02-14 4:19 ` Gyan Doshi [this message]
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=bd8de547-e40b-9d34-d283-a762adea2e4c@gyani.pro \
--to=ffmpeg@gyani.pro \
--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