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

Re: [PATCH 2/2] diffcore-rename: avoid processing duplicate destinations

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 27, 2015, 21:48 UTC
Message-ID
<xmqqr3tbhvqc.fsf@gitster.dls.corp.google.com>
In-Reply-To
<20150227014227.GB3210@peff.net>
Jeff King <peff@peff.net> writes:
> Like I mentioned before, I'm OK with not checking the actual diff output
> in the test. It's not like it was planned, and is just what diff_tree()
> happens to produce.  It does make sense, though....

When the topic is on processing broken input, I do not think "It does make sense, though." is a primary point, unless the result expected by these tests is the only possibly sane outcome (otherwise, another equally-sensible output will be rejected as a test failure). So I agree that there is a possibility that we might regret having the diff output tested here in the future when somebody further works in the area.

But let's not worry too much about it for now.
Thanks; the solution seems reasonable.
Previous: Jeff King
Message 12 of 12 in “[BUG] diffcore-rename with duplicate tree entries can segfault”
  1. Jeff KingFeb 24, 2015
  2. Junio C HamanoFeb 24, 2015
  3. Jeff KingFeb 24, 2015
  4. Junio C HamanoFeb 24, 2015
  5. Jeff KingFeb 24, 2015
  6. Junio C HamanoFeb 25, 2015
  7. Jeff KingFeb 25, 2015
  8. Junio C HamanoFeb 25, 2015
  9. 0/2 diffcore-rename with duplicate tree entries can segfaultJeff King, Feb 27, 2015
  10. 1/2 diffcore-rename: split locate_rename_dst into two functionsJeff King, Feb 27, 2015
  11. 2/2 diffcore-rename: avoid processing duplicate destinationsJeff King, Feb 27, 2015
  12. Junio C HamanoFeb 27, 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.