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

Re: [PATCH] Speed up history generation

From
LTLuben Tuikov <ltuikov@yahoo.com>
Date
Jul 1, 2006, 01:52 UTC
Message-ID
<20060701015204.17216.qmail@web31813.mail.mud.yahoo.com>
In-Reply-To
<7v3bdmglxo.fsf@assigned-by-dhcp.cox.net>
--- Junio C Hamano <junkio@cox.net> wrote:
Show 27 quoted lines
> Luben Tuikov <ltuikov@yahoo.com> writes:
> 
> > --- Junio C Hamano <junkio@cox.net> wrote:
> >...
> >> > @@ -2295,16 +2295,12 @@ sub git_history {
> >> >  	      "</div>\n";
> >> >  	print "<div class=\"page_path\"><b>/" . esc_html($file_name) . "</b><br/></div>\n";
> >> >  
> >> > -	open my $fd, "-|", "$gitbin/git-rev-list $hash | $gitbin/git-diff-tree -r --stdin --
> >> > \'$file_name\'";
> >> > -	my $commit;
> >> > +	open my $fd, "-|", "$gitbin/git-rev-list $hash -- \'$file_name\'";
> >> 
> >> This would speed things up but at the same time it changes the
> >> semantics because it involves merge simplification, no?
> >> 
> >> At least that should be noted in the commit log.
> >
> > Ok, I guess this should be in the log.  Can you add it please when
> > commiting to the master git branch?
> 
> Well, by "at least", what I meant was that it might make sense
> to pass "--full-history" option to be more compatible with the
> original output.  For graphical output like gitk, --full-history
> makes a mess on the screen, but a list-oriented output like
> gitweb it might be less confusing to show all the alternate
> paths that touched the path than leaving some histories out.
Ok, I can add the --full-history option, test it out and resubmit.
    Luben
Previous: Junio C HamanoNext: Linus Torvalds
Message 5 of 6 in “Speed up history generation”
  1. Speed up history generationLuben Tuikov, Jul 1, 2006
  2. Junio C HamanoJul 1, 2006
  3. Luben TuikovJul 1, 2006
  4. Junio C HamanoJul 1, 2006
  5. Luben TuikovJul 1, 2006
  6. Linus TorvaldsJul 1, 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.