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

Re: What's cooking in git.git (May 2018, #01; Mon, 7)

From
Junio C Hamano <gitster@pobox.com>
Date
May 10, 2018, 04:25 UTC
Message-ID
<xmqq603wkuh8.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<b58358de-3590-64b2-1db8-9cee9de92ed3@gmail.com>
Ben Peart <peartben@gmail.com> writes:
Show 11 quoted lines
> On 5/7/2018 10:58 AM, Junio C Hamano wrote:
>
>> * bp/merge-rename-config (2018-05-04) 3 commits
>>   - merge: pass aggressive when rename detection is turned off
>>   - merge: add merge.renames config setting
>>   - merge: update documentation for {merge,diff}.renameLimit
>>   (this branch uses en/rename-directory-detection-reboot.)
>>
>
> It isn't specifically called out here but is it safe to assume this is
> also headed to next behind en/rename-directory-detection-reboot?

Not really. A blank "what Junio will do to this topic?" verdict in any of these topic descriptions simply means I haven't made up my mind (spanning from "I merely queued it without reading it fully, only so that I won't lose it" to "I think it is OK but I haven't understood the implications of the change to the entire system").

Previous: Ben Peart
Message 8 of 8 in “What's cooking in git.git (May 2018, #01; Mon, 7)”
  1. Junio C HamanoMay 7, 2018
  2. Derrick StoleeMay 7, 2018
  3. Elijah NewrenMay 7, 2018
  4. Junio C HamanoMay 8, 2018
  5. Elijah NewrenMay 7, 2018
  6. Junio C HamanoMay 8, 2018
  7. Ben PeartMay 8, 2018
  8. Junio C HamanoMay 10, 2018

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.