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

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

From
Eyvind Bernhardsen <eyvind.bernhardsen@gmail.com>
Date
Jun 11, 2010, 20:56 UTC
Message-ID
<FD073505-FFF4-40D7-B841-0EC1B902E32E@gmail.com>
In-Reply-To
<7vd3vxicaw.fsf@alter.siamese.dyndns.org>
On 11. juni 2010, at 21.44, Junio C Hamano wrote:
Show 9 quoted lines
> Johannes Sixt <j.sixt@viscovery.net> writes:
> 
>> I know what your point is. It is still inappropriate to call
>> normalize_file() on data that comes from the repository. It is not the
>> task of a merge procedure to blindly normalize data.
> 
> It is not "blindly", but "running normalization one _extra time_, as the
> repository data is supposed to be canonical already", which is utterly
> wrong.
I agree that double normalization is evil, but the repository data isn't necessarily canonical if the configuration has changed since the data was added.
How do you feel about Finn Arne's idea of first convert_to_work_tree()-ing the data, then convert_to_git()ing it back?  That gets rid of the double normalization at the cost of some performance and memory usage (especially with CRLF output enabled).  I'm going to do some benchmarks to go along with my next stab at this.
- Eyvind
Previous: Junio C Hamano
Message 8 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.