Question about Source Control

[Chris Angelico]

On Fri, Mar 21, 2014 at 11:23 PM, Roy Smith <roy at panix.com> wrote:
> There's two things hg blame doesn't do which would be useful.
>
> First, the trivial one.  I don't want lines annotated by change number,
> I want them annotated by the name of the person who checked it in.  But,
> I'm sure that can be easily fixed with some simple post-processing
> filter, so it really falls into the bucket of "minor annoyances".
>
> The hard thing is I don't really want to know which change most recently
> touched the line of text.  I want to know who really wrote it.  It would
> be wonderful if hg were smart enough to be able to back-track through
> the change history and ignore trivial changes like whitespace,
> refactoring a function out of one file into another, etc.  That's the
> real meat and potatoes of "blame".  I want to know who I need to hit
> over the head with a clue-by-four once I fix a bug.

Hmm. 'git blame' can do both of those things, so I'd be very surprised
if 'hg blame' can't, at least with some extension(s). (The latter
feature is "git blame -w filename"; -w is a standard 'git diff' option
meaning "ignore whitespace".) But hey, if nothing else, you could
import your hg repo into git just to blame the file...

ChrisA