From: Junio C Hamano <junkio@cox.net>
To: Martin Langhoff <martin@catalyst.net.nz>
Cc: git@vger.kernel.org, Fredrik Kuivinen <freku045@student.liu.se>
Subject: Re: blame now knows -S
Date: Fri, 07 Apr 2006 02:32:05 -0700 [thread overview]
Message-ID: <7vu095k9yi.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7v1ww9loon.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Fri, 07 Apr 2006 02:28:40 -0700")
Junio C Hamano <junkio@cox.net> writes:
> I've made a few changes to "git blame" myself:
>
> - fix breakage caused by recent revision walker reorganization;
> - use built-in xdiff instead of spawning GNU diff;
> - implement -S <ancestry-file> like annotate does.
>
> Depending on the density of changes, it now appears that blame
> is 10%-30% faster than annotate. I thought CVS emulator might
> be interested to give it a whirl..
Sorry, forgot to mention... The updated blame will be in "next",
not in "master" yet.
next prev parent reply other threads:[~2006-04-07 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 9:28 blame now knows -S Junio C Hamano
2006-04-07 9:32 ` Junio C Hamano [this message]
2006-04-08 11:42 ` Fredrik Kuivinen
2006-04-08 13:53 ` Marco Costalba
2006-04-08 20:39 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vu095k9yi.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=freku045@student.liu.se \
--cc=git@vger.kernel.org \
--cc=martin@catalyst.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.