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: Ridley Combs <rcombs@rcombs.me>
Cc: Ridley Combs via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] lavf/assenc: normalize line endings to \n
Date: Tue, 13 Feb 2024 17:22:54 +0200 (EET)
Message-ID: <eaa2d7c-23dc-afae-687f-31d0e8f1e57d@martin.st> (raw)
In-Reply-To: <0F730CF2-5301-4AF9-9CAF-74F941D762C7@rcombs.me>

On Tue, 13 Feb 2024, Ridley Combs wrote:

> It looks like checkout has different behavior from reset, and fate uses a
> hard reset.
> To test, I committed the change adding tests/ref/** -text,
> unix2dos'd tests/ref/fate/sub-scc, then ran git -c core.autocrlf=true reset
> --quiet --hard; this dos2unix'd the file as expected when run with a working
> tree containing the .gitattributes change (but not otherwise).
> 
> 
> Git doesn't have any "memory" of the CRLFiness of a file beyond the content
> of the file itself (whether in the working tree or in committed blobs). It
> just doesn't necessarily replace every file in checkout invocations when
> they differ only in line endings. Windows was a mistake.

To rephrase; reset vs checkout doesn't make any difference here.

It seems to simply be the case, that as long as there are no changes to 
the file contents themselves between the relevant git commits, and the 
file isn't flagged as dirty in the stat cache of the local workdir, git 
never revisits the .gitattributes for this particular file.

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

      parent reply	other threads:[~2024-02-13 15:23 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ö
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ö [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=eaa2d7c-23dc-afae-687f-31d0e8f1e57d@martin.st \
    --to=martin@martin.st \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=rcombs@rcombs.me \
    /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