Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Martin Storsjö" <martin@martin.st>
To: ffmpeg-devel@ffmpeg.org
Cc: ffmpeg-cvslog@ffmpeg.org
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] lavf/assenc: normalize line endings to \n
Date: Mon, 12 Feb 2024 12:22:38 +0200 (EET)
Message-ID: <24dfac94-3f60-5454-19c9-0fc856c76@martin.st> (raw)
In-Reply-To: <20240212010139.5B289411B94@natalya.videolan.org>

On Mon, 12 Feb 2024, rcombs wrote:

> ffmpeg | branch: master | rcombs <rcombs@rcombs.me> | Sun Jan 28 14:27:17 2024 -0800| [7bf1b9b35769b37684dd2f18a54f01d852a540c8] | committer: rcombs
>
> lavf/assenc: normalize line endings to \n
>
> Previously, we produced output with either \r\n or mixed line endings.
> This was undesirable unto itself, but also made working with patches affecting
> FATE output particularly challenging, especially via the mailing list.
>
> Everything that consumes the SSA/ASS format is line-ending-agnostic,
> so \n is selected to simplify git/ML usage in FATE.
>
> Extra \r characters at the end of a packet are dropped. These are always
> ignored by the renderer anyway.
>
>> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=7bf1b9b35769b37684dd2f18a54f01d852a540c8
> ---
>
> .gitattributes                          |   1 -
> libavformat/assenc.c                    |  22 ++--
> tests/ref/fate/sub-aqtitle              |  94 ++++++++--------
> tests/ref/fate/sub-ass-to-ass-transcode | 124 ++++++++++-----------
> tests/ref/fate/sub-cc                   |  32 +++---
> tests/ref/fate/sub-cc-realtime          |  44 ++++----
> tests/ref/fate/sub-cc-scte20            |  34 +++---
> tests/ref/fate/sub-charenc              | 128 +++++++++++-----------
> tests/ref/fate/sub-jacosub              |  50 ++++-----
> tests/ref/fate/sub-microdvd             |  48 ++++-----
> tests/ref/fate/sub-movtext              |  34 +++---
> tests/ref/fate/sub-mpl2                 |  36 +++----
> tests/ref/fate/sub-mpsub                |  70 ++++++------
> tests/ref/fate/sub-mpsub-frames         |  32 +++---
> tests/ref/fate/sub-pjs                  |  34 +++---
> tests/ref/fate/sub-realtext             |  38 +++----
> tests/ref/fate/sub-sami                 |  46 ++++----
> tests/ref/fate/sub-sami2                | 186 ++++++++++++++++----------------
> tests/ref/fate/sub-srt                  | 102 +++++++++---------
> tests/ref/fate/sub-srt-badsyntax        |  48 ++++-----
> tests/ref/fate/sub-ssa-to-ass-remux     | 168 ++++++++++++++---------------
> tests/ref/fate/sub-stl                  |  62 +++++------
> tests/ref/fate/sub-subviewer            |  34 +++---
> tests/ref/fate/sub-subviewer1           |  48 ++++-----
> tests/ref/fate/sub-vplayer              |  34 +++---
> tests/ref/fate/sub-webvtt               |  58 +++++-----
> tests/ref/fate/sub-webvtt2              |  52 ++++-----
> 27 files changed, 831 insertions(+), 828 deletions(-)
>
> diff --git a/.gitattributes b/.gitattributes
> index 5a19b963b6..a900528e47 100644
> --- a/.gitattributes
> +++ b/.gitattributes
> @@ -1,2 +1 @@
> *.pnm -diff -text
> -tests/ref/fate/sub-scc eol=crlf

This change seems to have had a tricky effect on the 
tests/ref/fate/sub-scc file. Previously, when checked out, users got the 
file with CRLF newlines. When updating to this git commit, or past it, 
that file remains untouched, with CRLF still present, and the 
fate-sub-scc test fails. If one does "rm tests/ref/fate/sub-scc; git 
checkout tests/ref/fate/sub-scc", then the file does get restored with LR 
newlines, and the test passes.

It's easy to do this change manually in the source checkout of a fate 
runner, but I'm not sure how easily we get all fate instances fixed that 
way - currently this test is failing in most of them.

// Martin

_______________________________________________
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:[~2024-02-12 10:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240212010139.5B289411B94@natalya.videolan.org>
2024-02-12 10:22 ` Martin Storsjö [this message]
2024-02-12 10:51   ` Hendrik Leppkes
2024-02-12 11:31     ` Martin Storsjö
2024-02-13  9:28       ` Anton Khirnov
2024-02-13 12:08         ` Ridley Combs via ffmpeg-devel
2024-02-13 12:33           ` Martin Storsjö
2024-02-13 12:48             ` Ridley Combs via ffmpeg-devel
2024-02-13 13:29               ` Martin Storsjö
2024-02-13 15:22               ` Martin Storsjö

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=24dfac94-3f60-5454-19c9-0fc856c76@martin.st \
    --to=martin@martin.st \
    --cc=ffmpeg-cvslog@ffmpeg.org \
    --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