[Ksummit-discuss] [CORE TOPIC] Recruitment (Reviewers, Testers, Maintainers, Hobbyists)

[James Bottomley]

On Wed, 2015-07-22 at 10:10 -0400, Steven Rostedt wrote:
> On Wed, 22 Jul 2015 08:57:34 -0500
> Bjorn Helgaas <bhelgaas at google.com> wrote:
> 
> 
> > > Ah! that's the change I was looking for!
> > 
> > I don't know if you'd find this more work or less, but I use "git log
> > -p foo.c" for this instead of git blame.  Unless there's been a rename
> > or a move between files, one invocation is usually enough.
> 
> I've used "git log -p foo.c" before, but I find that some of my files I
> work with, that is way too much info. Especially, when the commit I'm
> looking for happens to be years old. I use the log -p for when I know
> the change has been recent.

I think what we need is a git log --line <name> <path> which would track
the commits that touched a given line in <path> (hopefully even across
renames).  It shouldn't be too hard to come up with that.

James