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

Re: [PATCH 0/4] Blame in reverse

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Apr 3, 2008, 11:25 UTC
Message-ID
<47F4BE98.8060209@viscovery.net>
In-Reply-To
<7v4paj486a.fsf@gitster.siamese.dyndns.org>
Junio C Hamano schrieb:
Show 5 quoted lines
> Usual "git blame" starts from the latest revision and finds where each
> line came from (i.e. who came up with that brilliant idea, or more often
> who introduced that bug).  This new mode starts from an old revision, and
> annotates in reverse --- up to which point each line survived, before it
> got replaced with something else. 
Nice!! Is the result somehow different from
	$ git rev-list --reverse HEAD > /tmp/blame.revs
	$ git blame -S /tmp/blame.revs foo.c
?
-- Hannes
Previous: Junio C HamanoNext: Junio C Hamano
Message 7 of 8 in “Blame in reverse”
  1. 0/4 Blame in reverseJunio C Hamano, Apr 3, 2008
  2. 1/4 "log" and friends: --children optionJunio C Hamano, Apr 3, 2008
  3. Johannes SchindelinApr 3, 2008
  4. 2/4 builtin-blame.c: move prepare_final() into a separate function.Junio C Hamano, Apr 3, 2008
  5. 3/4 builtin-blame.c: allow more than 16 parentsJunio C Hamano, Apr 3, 2008
  6. 4/4 git-blame --reverseJunio C Hamano, Apr 3, 2008
  7. Johannes SixtApr 3, 2008
  8. Junio C HamanoApr 3, 2008

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.