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

Re: [RFC] ll-merge: Normalize files before merging

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Jun 11, 2010, 05:49 UTC
Message-ID
<4C11CE75.7080706@viscovery.net>
In-Reply-To
<1276202894-11805-1-git-send-email-eyvind.bernhardsen@gmail.com>
Am 6/10/2010 22:48, schrieb Eyvind Bernhardsen:
Show 7 quoted lines
> Currently, merging across changes in line ending normalization is
> painful since all lines containing CRLF will conflict uselessly.
> 
> Fix ll-merge so that the "base", "theirs" and "ours" files are passed
> through convert_to_git() before a three-way merge.  This prevents
> differences that can be normalized away from blocking an automatic
> merge.

I think you are going overboard here. Normalization should only happen only for data that moves from the worktree to the database. But during a merge, at most one part can come from the worktree, methinks; you are normalizing all three of them, though.

Show 8 quoted lines
> This patch has already been useful to me, but I'm not sure it is the
> best possible solution to the problem (especially in terms of
> efficiency), hence the RFC.
> 
> Note that clean and ident filters will also be run, which might be a
> good thing.  Also, the tests require my crlf/text series from pu.
> --
> Eyvind

Please do not put a dash-dash-blank line before the patch; Thunderbird takes it as the beginning of the signature and truncates the message in the reply.

-- Hannes
Previous: Eyvind BernhardsenNext: Eyvind Bernhardsen
Message 2 of 8 in “[RFC] ll-merge: Normalize files before merging”
  1. Eyvind BernhardsenJun 10, 2010
  2. Johannes SixtJun 11, 2010
  3. Eyvind BernhardsenJun 11, 2010
  4. Johannes SixtJun 11, 2010
  5. Finn Arne GangstadJun 11, 2010
  6. Eyvind BernhardsenJun 11, 2010
  7. Junio C HamanoJun 11, 2010
  8. Eyvind BernhardsenJun 11, 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.