--- Junio C Hamano <junkio@xxxxxxx> wrote:
> Luben Tuikov <ltuikov@xxxxxxxxx> writes:
>
> > --- Junio C Hamano <junkio@xxxxxxx> 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
-
: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html