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

[Josh Triplett]

On Wed, Jul 22, 2015 at 09:04:57AM -0400, Steven Rostedt wrote:
> On Tue, 21 Jul 2015 18:54:36 +1000
> NeilBrown <neilb at suse.com> wrote:
> 
> > On Tue, 21 Jul 2015 10:00:33 +0800 Zefan Li <lizefan at huawei.com> wrote:
> > 
> > > > Then it should just be case of of asking Stephen to "put this tree last
> > > > in linux-next", and Linus to "pull this one last, right before
> > > > releasing -rc1". And getting the timing right for the script to run.
> > > > 
> > > 
> > > This makes git-blame less useful, and that's one of the reasons some
> > > maintainers don't like trivial cleanups.
> > 
> > Sounds like we need to propose an enhancement to "git-blame"...
> > 
> 
> No need. I use git blame all the time. Trivial patches don't bother me.
> 
> $ git blame foo.c
> 
> $ git show abc123
> 
> Sees that it's a trivial fix
> 
> $ git blame abc123~1 foo.c
> 
> $ git show def890

If you use vim, try vim-fugitive for this.  While editing a file,
:Gblame to get the blame info.  Hit o in the blame window to open a
commit, showing the commit message and patch, automatically jumping to
the patch line that changed the line you're looking at.  If that's not
the commit you want, hit P in the blame window to re-blame from the
parent of that commit.

- Josh Triplett