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

Re: What's cooking in git.git (Jun 2017, #06; Thu, 22)

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 24, 2017, 01:01 UTC
Message-ID
<xmqqwp829p18.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<xmqq60fmb4q8.fsf@gitster.mtv.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
> But for the purpose of this "moved line coloring",
> excluding multiple copy destinations of the same thing may be a
> simpler and more robust solution.  It will not catch "somebody
> stupidly removed one function and made two private copies", though.

Let me take this one back. Treating multiple copy destinations and multiple copy sources differently is a bad idea. It is easy for a user to give "-R" option to "diff" to turn such a stupid patch into "somebody brilliantly consolidated two copies of the same thing into a single function", and we want to keep "diff" and "diff -R" output symmetric.

Previous: Junio C HamanoNext: Stefan Beller
Message 9 of 12 in “What's cooking in git.git (Jun 2017, #06; Thu, 22)”
  1. Junio C HamanoJun 22, 2017
  2. Ævar Arnfjörð BjarmasonJun 22, 2017
  3. Junio C HamanoJun 23, 2017
  4. Junio C HamanoJun 24, 2017
  5. Lars SchneiderJun 23, 2017
  6. Ævar Arnfjörð BjarmasonJun 23, 2017
  7. Stefan BellerJun 23, 2017
  8. Junio C HamanoJun 24, 2017
  9. Junio C HamanoJun 24, 2017
  10. Stefan BellerJun 27, 2017
  11. Junio C HamanoJun 24, 2017
  12. Stefan BellerJun 24, 2017

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.