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

Re: [PATCH 1/1] cvsexportcommit: force crlf translation

From
Junio C Hamano <gitster@pobox.com>
Date
May 7, 2019, 14:02 UTC
Message-ID
<xmqqd0kul5w0.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<4da677fb-47c3-a1ac-e7e0-6b74cdb7334c@virtualroadside.com>
Dustin Spicuzza <dustin@virtualroadside.com> writes:
Show 7 quoted lines
> Yes, your interpretation is exactly correct, even the interpretation of
> the uncertainty of the message.
>
> I didn't send the patch to this list though, not sure why gitgitgadget
> decided to do so (I've never heard of it before now). The patch was
> originally submitted to git for windows (PR #938), with an even worse
> commit message. :)

The credit goes to Dscho, making effort to slim down patches Git for Windows carries on top of my tree by upstreaming them.

Previous: Dustin SpicuzzaNext: Johannes Schindelin
Message 5 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.