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

Re: [PATCH] xmerge.c: fix xdl_merge to conform with the manual

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 8, 2015, 08:06 UTC
Message-ID
<xmqqtwxvsyjq.fsf@gitster.dls.corp.google.com>
In-Reply-To
<54F95F25.9090300@gmail.com>
Anton Trunov <anton.a.trunov@gmail.com> writes:
> On 04/03/15 23:01, Junio C Hamano wrote:
>
> My apologies for pushing this topic, but what would you recommend?
> Should we treat both sides line-wise or should we correct the documentation?

My gut feeling is that the change to swap which side is examined first would end up to be a patch to rob Peter to pay Paul, and a line-by-line approach might end up paying too expensive a runtime cost in practice (and it should not really matter which side's whitespace the end result matches, because the user says "I do not care about whitespace changes", so paying that cost is not something we would want to do). So it may be that the best course of action may be documentation updates.

But I haven't had a chance to think about it through yet to form a definite opinion.

Thanks.
Previous: Anton TrunovNext: Anton Trunov
Message 12 of 13 in “xmerge.c: fix xdl_merge to conform with the manual”
  1. xmerge.c: fix xdl_merge to conform with the manualAnton Trunov, Mar 3, 2015
  2. Torsten BögershausenMar 3, 2015
  3. Eric SunshineMar 4, 2015
  4. Anton TrunovMar 4, 2015
  5. Eric SunshineMar 4, 2015
  6. Anton TrunovMar 4, 2015
  7. Junio C HamanoMar 3, 2015
  8. Anton TrunovMar 4, 2015
  9. Junio C HamanoMar 4, 2015
  10. Anton TrunovMar 5, 2015
  11. Anton TrunovMar 6, 2015
  12. Junio C HamanoMar 8, 2015
  13. Anton TrunovMar 9, 2015

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.