Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Oneric <oneric@oneric.de>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 0/3] Some small ASS conversion fixes
Date: Thu, 1 Dec 2022 07:01:03 +0100
Message-ID: <Y4hDHwFTRT4X2Qsa@oneric.de> (raw)
In-Reply-To: <Y3lxpdtfSldOk8MQ@oneric.de>


[-- Attachment #1.1: Type: text/plain, Size: 1348 bytes --]

On Sun, Nov 20, 2022 at 01:15:33 +0100, Oneric wrote:
> On Sun, Nov 13, 2022 at 20:57:15 +0100, Oneric wrote:
> > This fixes colours and font selection for files converted to ASS
> 
> Ping.
> 
> As a reminder v1 and v2 are equivalent and patchwork is buggy and can
> thus neither apply v1 or v2 and its results can be ignored and its patch
> or diff downloads should not be used, because they are corrupted.
> 
> v1 can be applied from the mails received from the list, v2 can be applied
> the same way for patch one and two, but you may need to use --keep-cr and
> because it turns out not only patchwork but also the mailinglist software
> mangles the transfer encoding, patch three of v2 cannot applied from the
> Mail received by the list.
> As an alternative I previously attached an archive (so the list won’t
> mangle it again) containing the three format-patch files, see:
>   https://ffmpeg.org/pipermail/ffmpeg-devel/2022-November/303904.html
> 
> As before, if you’d prefer to get a v3 where all mails can be applied from
> the list directly and no binary diff is used, tell me and I’ll send a v3
> forcing base64-encoding from git send-email and including some non-ASCII
> characters in the patch comment, since this appeared to make the list keep
> the base64 transfer-encoding for patch 2 v2.

Ping #2

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

  reply	other threads:[~2022-12-01  6:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13 19:57 Oneric
2022-11-13 19:57 ` [FFmpeg-devel] [PATCH v2 1/3] avcodec/ass: fix comment Oneric
2022-11-13 19:57 ` [FFmpeg-devel] [PATCH v2 2/3] avcodec/ass: accurately preserve colours Oneric
2022-11-13 19:57 ` [FFmpeg-devel] [PATCH v2 3/3] avcodec/ass: specify a permissive encoding Oneric
2022-11-13 20:15   ` Oneric
2022-11-13 22:14     ` Oneric
2022-11-13 20:15 ` [FFmpeg-devel] [PATCH v2 0/3] Some small ASS conversion fixes Soft Works
2022-11-13 20:27   ` Oneric
2022-11-13 21:00     ` Oneric
2022-11-13 21:03       ` Soft Works
2022-11-13 21:01     ` Soft Works
2022-11-13 21:57       ` Oneric
2022-11-14 18:52         ` Oneric
2022-11-20  0:15 ` Oneric
2022-12-01  6:01   ` Oneric [this message]
2022-12-01 12:30     ` Paul B Mahol

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=Y4hDHwFTRT4X2Qsa@oneric.de \
    --to=oneric@oneric.de \
    --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