From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 6AB7A405 for ; Wed, 22 Jul 2015 14:44:12 +0000 (UTC) Received: from bedivere.hansenpartnership.com (bedivere.hansenpartnership.com [66.63.167.143]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 1F42312D for ; Wed, 22 Jul 2015 14:44:12 +0000 (UTC) Message-ID: <1437576250.2171.19.camel@HansenPartnership.com> From: James Bottomley To: Steven Rostedt Date: Wed, 22 Jul 2015 07:44:10 -0700 In-Reply-To: <1437576121.2171.17.camel@HansenPartnership.com> References: <20150717101151.5d5bc86d@lwn.net> <20150717133712.42c82add@gandalf.local.home> <20150717190223.GB1499@cloud> <20150717154326.6f129bc4@gandalf.local.home> <20150717202412.GA1856@cloud> <20150717163903.67747d86@gandalf.local.home> <20150717204856.GA2048@cloud> <20150717165501.62ed4e04@gandalf.local.home> <1437376105.8968.14.camel@HansenPartnership.com> <20150720084420.GA11454@x> <1437384215.8968.28.camel@HansenPartnership.com> <1437386699.22996.10.camel@infradead.org> <1437388227.8968.34.camel@HansenPartnership.com> <1437390546.22996.27.camel@infradead.org> <55ADA7C1.3050809@huawei.com> <20150721185436.20b97c47@notabene.brown> <20150722090457.45562610@gandalf.local.home> <20150722101039.2ce09fd7@gandalf.local.home> <1437576121.2171.17.camel@HansenPartnership.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: "ksummit-discuss@lists.linuxfoundation.org" , Dan Carpenter , Jason Cooper Subject: Re: [Ksummit-discuss] [CORE TOPIC] Recruitment (Reviewers, Testers, Maintainers, Hobbyists) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 2015-07-22 at 07:42 -0700, James Bottomley wrote: > On Wed, 2015-07-22 at 10:10 -0400, Steven Rostedt wrote: > > On Wed, 22 Jul 2015 08:57:34 -0500 > > Bjorn Helgaas 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 which would track > the commits that touched a given line in (hopefully even across > renames). It shouldn't be too hard to come up with that. Well, duh, we do, it's git log -L ... I take it no-one uses it because like me, no-one knows about it? James