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

Re: how to track the history of a line in a file

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 2, 2009, 22:54 UTC
Message-ID
<7vvdsxb9oh.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<alpine.DEB.1.10.0901021544580.21567@asgard.lang.hm>
david@lang.hm writes:
> I was misunderstanding git blame

You may find the --porcelain output format of git-blame useful to make your script safer and more robust.

Previous: david@lang.hmNext: david@lang.hm
Message 8 of 17 in “how to track the history of a line in a file”
  1. david@lang.hmJan 2, 2009
  2. Jeff KingJan 2, 2009
  3. david@lang.hmJan 2, 2009
  4. Jeff WhitesideJan 2, 2009
  5. david@lang.hmJan 2, 2009
  6. david@lang.hmJan 2, 2009
  7. david@lang.hmJan 2, 2009
  8. Junio C HamanoJan 2, 2009
  9. david@lang.hmJan 3, 2009
  10. Thomas RastJan 3, 2009
  11. david@lang.hmJan 3, 2009
  12. david@lang.hmJan 2, 2009
  13. david@lang.hmJan 3, 2009
  14. Bernt HansenJan 6, 2009
  15. Miklos VajnaJan 6, 2009
  16. Bernt HansenJan 6, 2009
  17. Bernt HansenJan 6, 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.