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
Anton Trunov <anton.a.trunov@gmail.com>
Date
Mar 6, 2015, 08:02 UTC
Message-ID
<54F95F25.9090300@gmail.com>
In-Reply-To
<xmqqfv9k8rcs.fsf@gitster.dls.corp.google.com>
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?

Current version for git help merge:
...
ignore-space-change, ignore-all-space, ignore-space-at-eol
    Treats lines with the indicated type of whitespace change as
unchanged for the sake of a three-way merge. Whitespace
    changes mixed with other changes to a line are not ignored. See also
git-diff(1)-b, -w, and --ignore-space-at-eol.
    o   If their version only introduces whitespace changes to a line,
our version is used;
    o   If our version introduces whitespace changes but their version
includes a substantial change, their version is used;
    o   Otherwise, the merge proceeds in the usual way.
...
The 1st bullet point could be changed into
    o   If their version only introduces whitespace changes to *all
changed lines*, our version is used;
And the 2nd one into:
    o   If our version only introduces whitespace changes to all changed
lines, but their version includes at least one substantially changed
line, all lines from their version are used;
Previous: Anton TrunovNext: Junio C Hamano
Message 11 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.