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

Re: What's in git.git

From
Fredrik Kuivinen <freku045@student.liu.se>
Date
Mar 10, 2006, 10:44 UTC
Message-ID
<20060310104443.GA4491@c165.ib.student.liu.se>
In-Reply-To
<46a038f90603060105m29595745ke64d4a623506c0b0@mail.gmail.com>
On Mon, Mar 06, 2006 at 10:05:41PM +1300, Martin Langhoff wrote:
Show 7 quoted lines
> On 3/6/06, Junio C Hamano <junkio@cox.net> wrote:
> > - The deathmatch between annotate/blame (Ryan Anderson, Fredrik
> >   Kuivinen, me cheerleading)
> 
> Add fuel to the fire  ;-) Can git-blame take cached git-rev-list
> output like annotate does with -S?
>

Currently it cannot do that. How is that option used? If you want to make annotate/blame faster for certain files you might as well cache the output of annotate/blame instead of the git-rev-list output, no?

What am I missing?
- Fredrik
Previous: Martin LanghoffNext: Johannes Schindelin
Message 4 of 9 in “What's in git.git”
  1. Junio C HamanoMar 6, 2006
  2. blame: unbreak "diff -U 0".Junio C Hamano, Mar 6, 2006
  3. Martin LanghoffMar 6, 2006
  4. Fredrik KuivinenMar 10, 2006
  5. Johannes SchindelinMar 10, 2006
  6. Martin LanghoffMar 10, 2006
  7. Junio C HamanoMar 13, 2006
  8. Johannes SchindelinMar 6, 2006
  9. Lukas SandströmMar 6, 2006

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.