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

Re: [ANNOUNCE] tig-0.14

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 7, 2009, 07:28 UTC
Message-ID
<7vprhuzoxm.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20090207071056.GB14856@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
> My impression is that tig is currently doing (1).  I think (2) will
> suffer from the same problem, but in practice the margin of error will
> be much smaller because your are rewinding through fewer changes. So if
> that is what you were suggesting, I think it is probably worth trying.

It has been quite a while since I did the "show previous" feature of "git-blame --porcelain" that has been forever queued in 'next'; if I remember correctly, it implemented (2).

The reason why it never graduated from 'next' is exactly this issue. By definition, there is no "previous" line number (if there were such a thing that says "This line was at line N in the parent of the blamed commit", then the commit wouldn't have taken the blame but would have passed it down to the parent), and we need to come up with a reasonable heuristics.

So perhaps this discussion would motivate somebody to finish that part off, and tig and other Porcelains can just read the necessary line number from the git-blame output.

Previous: Jeff KingNext: david@lang.hm
Message 14 of 69 in “[ANNOUNCE] tig-0.14”
  1. Jonas FonsecaFeb 5, 2009
  2. bill lamFeb 6, 2009
  3. Jonas FonsecaFeb 6, 2009
  4. Sitaram ChamartyFeb 6, 2009
  5. Jonas FonsecaFeb 8, 2009
  6. showing SHA1 of parent commit in tig [was Re: [ANNOUNCE] tig-0.14Sitaram Chamarty, Feb 11, 2009
  7. Jonas FonsecaFeb 12, 2009
  8. Sitaram ChamartyFeb 12, 2009
  9. Jeff KingFeb 6, 2009
  10. Jonas FonsecaFeb 6, 2009
  11. Jakub NarebskiFeb 6, 2009
  12. Jonas FonsecaFeb 8, 2009
  13. Jeff KingFeb 7, 2009
  14. Junio C HamanoFeb 7, 2009
  15. david@lang.hmFeb 7, 2009
  16. Jonas FonsecaFeb 8, 2009
  17. Jonas FonsecaFeb 8, 2009
  18. Jeff KingFeb 8, 2009
  19. Jonas FonsecaFeb 8, 2009
  20. Jeff KingFeb 7, 2009
  21. Jonas FonsecaFeb 8, 2009
  22. Jeff KingFeb 8, 2009
  23. Jonas FonsecaFeb 8, 2009
  24. Mikael MagnussonFeb 7, 2009
  25. Peter BaumannFeb 9, 2009
  26. Jeff KingFeb 9, 2009
  27. Peter BaumannFeb 9, 2009
  28. Jonas FonsecaFeb 10, 2009
  29. Jari AaltoFeb 10, 2009
  30. Ted PavlicFeb 10, 2009
  31. Jonas FonsecaFeb 10, 2009
  32. Brian GernhardtFeb 10, 2009
  33. Stefan KarpinskiFeb 10, 2009
  34. Jonas FonsecaFeb 10, 2009
  35. Brian GernhardtFeb 10, 2009
  36. Jonas FonsecaFeb 10, 2009
  37. Brian GernhardtFeb 10, 2009
  38. Ted PavlicFeb 11, 2009
  39. Jonas FonsecaFeb 12, 2009
  40. Ted PavlicFeb 11, 2009
  41. Ted PavlicFeb 20, 2009
  42. Jonas FonsecaFeb 20, 2009
  43. Ted PavlicFeb 20, 2009
  44. Jonas FonsecaFeb 20, 2009
  45. Jonas FonsecaFeb 25, 2009
  46. Ted PavlicFeb 11, 2009
  47. Ted PavlicFeb 11, 2009
  48. Ted PavlicFeb 11, 2009
  49. Jonas FonsecaFeb 12, 2009
  50. Tilo SchwarzFeb 12, 2009
  51. Jonas FonsecaFeb 12, 2009
  52. Tilo SchwarzFeb 12, 2009
  53. Jonas FonsecaFeb 15, 2009
  54. Sitaram ChamartyFeb 16, 2009
  55. Jonas FonsecaFeb 16, 2009
  56. Sitaram ChamartyFeb 16, 2009
  57. Thomas AdamFeb 16, 2009
  58. Jonas FonsecaFeb 16, 2009
  59. Marco CostalbaFeb 17, 2009
  60. Tilo SchwarzFeb 16, 2009
  61. Jonas FonsecaFeb 20, 2009
  62. Tilo SchwarzFeb 21, 2009
  63. Jonas FonsecaFeb 21, 2009
  64. Tilo SchwarzFeb 21, 2009
  65. Tilo SchwarzFeb 16, 2009
  66. bill lamFeb 13, 2009
  67. Jonas FonsecaFeb 13, 2009
  68. bill lamFeb 14, 2009
  69. Jonas FonsecaFeb 15, 2009

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.