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

Re: gsoc - Better git log --follow support

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 23, 2011, 18:12 UTC
Message-ID
<7vk4fpemei.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20110323170655.GA4392@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> Obviously a solution that always provides an exact right answer is
> preferable to "pretty good results", but we'd have to keep in mind the
> performance difference.

And that is why the current --follow hack was declared to be good enough to give "pretty good results" by its inventor, no?

I still agree with it personally, and if we _were_ to improve it out of "hack" status, we should aim to do the right thing (provided if there is a "right thing" exists).

Previous: Jeff KingNext: Jeff King
Message 8 of 12 in “gsoc - Better git log --follow support”
  1. Michał ŁowickiMar 19, 2011
  2. Jakub NarebskiMar 19, 2011
  3. Jeff KingMar 21, 2011
  4. Michał ŁowickiMar 22, 2011
  5. Jeff KingMar 23, 2011
  6. Junio C HamanoMar 23, 2011
  7. Jeff KingMar 23, 2011
  8. Junio C HamanoMar 23, 2011
  9. Jeff KingMar 23, 2011
  10. Michał ŁowickiApr 13, 2011
  11. Jonathan NiederApr 15, 2011
  12. Michał ŁowickiApr 15, 2011

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.