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

Re: [PATCH v5 0/3] merge-recursive: option to disable renames

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 21, 2016, 07:40 UTC
Message-ID
<xmqq7fhya4v5.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<1456022072-5342-1-git-send-email-felipegassis@gmail.com>

Yikes, your previous round is already in 'next', so could you make this series an incremental on top of what is already queued up to 1b47ad16 (merge-recursive: more consistent interface, 2016-02-17)?

Thanks.
Previous: Felipe Gonçalves AssisNext: Felipe Gonçalves Assis
Message 5 of 6 in “merge-recursive: option to disable renames”
  1. 0/3 merge-recursive: option to disable renamesFelipe Gonçalves Assis, Feb 21, 2016
  2. 1/3 merge-recursive: test rename threshold optionFelipe Gonçalves Assis, Feb 21, 2016
  3. 2/3 merge-recursive: option to disable renamesFelipe Gonçalves Assis, Feb 21, 2016
  4. 3/3 merge-recursive: more consistent interfaceFelipe Gonçalves Assis, Feb 21, 2016
  5. Junio C HamanoFeb 21, 2016
  6. Felipe Gonçalves AssisFeb 21, 2016

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.