git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 0/1] Fix cvsexportcommit with CR/LF line endings

From
Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Date
Apr 29, 2019, 21:58 UTC
Message-ID
<pull.132.git.gitgitgadget@gmail.com>

When using CVSNT, we need to be prepared to grok CVS output with CR/LF line endings.

While we do not use CVSNT in Git for Windows, this patch made its way into Git's source code via the Git for Windows project (probably because of the ease of GitHub PRs), and we had not a single complaint for over 2 years, so I would consider this patch ready to be included in core Git.

Dustin Spicuzza (1):
  cvsexportcommit: force crlf translation
 git-cvsexportcommit.perl | 1 +
 1 file changed, 1 insertion(+)
base-commit: 39ffebd23b1ef6830bf86043ef0b5c069d9299a9
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-132%2Fdscho%2Fcvsexportcommit-crlf-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-132/dscho/cvsexportcommit-crlf-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/132
-- 
gitgitgadget
Next: Dustin Spicuzza via GitGitGadget
Message 1 of 7 in “Fix cvsexportcommit with CR/LF line endings”
  1. 0/1 Fix cvsexportcommit with CR/LF line endingsJohannes Schindelin via GitGitGadget, Apr 29, 2019
  2. 1/1 cvsexportcommit: force crlf translationDustin Spicuzza via GitGitGadget, Apr 29, 2019
  3. Junio C HamanoMay 7, 2019
  4. Dustin SpicuzzaMay 7, 2019
  5. Junio C HamanoMay 7, 2019
  6. Johannes SchindelinMay 8, 2019
  7. Junio C HamanoMay 8, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.