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

Re: [Possible GIT Bug]

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 10, 2018, 16:03 UTC
Message-ID
<xmqqin3duypt.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20180910132452.GB5233@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 5 quoted lines
> Your explanation is correct. To be fair, though, it seems like
> --find-copies-harder is made a lot less useful by the not considering
> the larger set of sources, since that's kind of its point. I'm not sure
> if this behavior actually is intentional, or simply what happens to
> occur based on the combination of features.

It is neither but if I have to pick one between the two, it is much closer to the former than the latter. The primary source of this is that we have only *one* pathspec given to the diff machinery, but in order to implement your ideal "find harder", you'd need *two*. That is, one set of paths for which you are interested in their origin, and the other set that you allow the machinery to consider as possible origins. Since we can only give one pathspec machinery, that one pathspec is used to specify both of these sets.

Previous: Jeff KingNext: Eckhard Maaß
Message 4 of 6 in “Fwd: [Possible GIT Bug]”
  1. Dylan YoungSep 9, 2018
  2. Bryan TurnerSep 9, 2018
  3. Jeff KingSep 10, 2018
  4. Junio C HamanoSep 10, 2018
  5. Eckhard MaaßSep 10, 2018
  6. Junio C HamanoSep 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.