Skip to content

Normalize README-3.0.md to LF line endings#17632

Open
jslobodzian wants to merge 1 commit into
3.0-devfrom
users/joslobo/normalize-readme-3.0-lf
Open

Normalize README-3.0.md to LF line endings#17632
jslobodzian wants to merge 1 commit into
3.0-devfrom
users/joslobo/normalize-readme-3.0-lf

Conversation

@jslobodzian
Copy link
Copy Markdown
Collaborator

The README-3.0.md file currently has CRLF line endings on the 3.0 and 3.0-dev branches, while fasttrack/3.0 has LF (normalized during a prior merge-conflict resolution — commit 1392776).

This caused a confusing whole-file diff between 3.0 and fasttrack/3.0 that GitHub hides by default but shows up in any local git diff.

This PR normalizes to LF on 3.0-dev (the repo has core.autocrlf=true, so this is just git add --renormalize). Content is byte-identical aside from the stripped CRs.

After this lands and flows into 3.0, the cosmetic diff with fasttrack/3.0 will disappear.

The file currently has CRLF line endings on 3.0 and 3.0-dev, while
fasttrack/3.0 has LF (normalized during a prior merge-conflict
resolution). The repo has core.autocrlf=true; this commit uses
`git add --renormalize` to align with the standard.

Content is byte-identical apart from the EOL stripping.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@jslobodzian jslobodzian requested a review from a team as a code owner June 5, 2026 14:31
@microsoft-github-policy-service microsoft-github-policy-service Bot added the 3.0-dev PRs Destined for AzureLinux 3.0 label Jun 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3.0-dev PRs Destined for AzureLinux 3.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants