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

Re: [PATCH v2] autocrlf: Make it work also for un-normalized repositories

From
Clemens Buchacher <drizzd@aon.at>
Date
May 23, 2010, 09:30 UTC
Message-ID
<20100523093040.GA15602@localhost>
In-Reply-To
<20100511223757.GB16974@pvv.org>
On Wed, May 12, 2010 at 12:37:57AM +0200, Finn Arne Gangstad wrote:
Show 5 quoted lines
> Change autocrlf to not do any conversions to files that in the
> repository already contain a CR. git with autocrlf set will never
> create such a file, or change a LF only file to contain CRs, so the
> (new) assumption is that if a file contains a CR, it is intentional,
> and autocrlf should not change that.

I think this is a good change. But it only covers the part where we translate CR -> LF when staging changes. With Eyvind's patches, if I understand correctly, it will be possible to convert files to have LF line endings. Such files will be translated from LF -> CR when adding changes.

So if the file already has LF line endings, will this cause the same problem the other way around?

Clemens
Previous: Hnerik Grubbström
Message 5 of 5 in “autocrlf: Make it work also for un-normalized repositories”
  1. autocrlf: Make it work also for un-normalized repositoriesFinn Arne Gangstad, May 11, 2010
  2. Dmitry PotapovMay 12, 2010
  3. Eyvind BernhardsenMay 12, 2010
  4. Hnerik GrubbströmMay 12, 2010
  5. Clemens BuchacherMay 23, 2010

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.