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

Re: [PATCH 5/8] rerere: use ll_merge() instead of using xdl_merge()

From
Johannes Sixt <j6t@kdbg.org>
Date
Jan 17, 2010, 20:40 UTC
Message-ID
<201001172140.13802.j6t@kdbg.org>
In-Reply-To
<7v4omk8sjg.fsf@alter.siamese.dyndns.org>
On Sonntag, 17. Januar 2010, Junio C Hamano wrote:
> So I didn't think using ll_merge() makes things worse, and that was the
> reason why I did it this way.

Thinking a bit more about it, the problematic point is not that a custom merge driver is used, but it is the way how conflicts are marked. For example, it seems a bit strange that an XML merge driver would mark-up conflicts using <<<<<<< and >>>>>>> in random points of XML text, when it knows that the result would be invalid XML (and subsequently an XML editor could fail to parse the result). It would be more apropriate when it used a different way to mark conflicts.

The conclusion is that your approach goes in the right direction. But since the result depends on the traditional conflict markers, it keeps rerere tied to the standard text merge driver. The capability that rerere will use custom merge drivers is of little use (unless the merge driver uses standard conflict markers); that it allows attributes for the standard text merge, is, of course, a plus.

-- Hannes
Previous: Junio C HamanoNext: Junio C Hamano
Message 9 of 13 in “Rescuing repeated merge of Documentation/git-merge.txt”
  1. 0/8 Rescuing repeated merge of Documentation/git-merge.txtJunio C Hamano, Jan 17, 2010
  2. 1/8 git_attr(): fix function signatureJunio C Hamano, Jan 17, 2010
  3. 2/8 xdl_merge(): introduce xmparam_t for merge specific parametersJunio C Hamano, Jan 17, 2010
  4. 3/8 xdl_merge(): allow passing down marker_size in xmparam_tJunio C Hamano, Jan 17, 2010
  5. 4/8 merge-tree: use ll_merge() not xdl_merge()Junio C Hamano, Jan 17, 2010
  6. 5/8 rerere: use ll_merge() instead of using xdl_merge()Junio C Hamano, Jan 17, 2010
  7. Johannes SixtJan 17, 2010
  8. Junio C HamanoJan 17, 2010
  9. Johannes SixtJan 17, 2010
  10. 6/8 conflict-marker-size: new attributeJunio C Hamano, Jan 17, 2010
  11. 7/8 rerere: prepare for customizable conflict marker lengthJunio C Hamano, Jan 17, 2010
  12. 8/8 rerere: honor conflict-marker-size attributeJunio C Hamano, Jan 17, 2010
  13. Junio C HamanoJan 17, 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.