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 862D51BB for ; Wed, 22 Jul 2015 15:04:10 +0000 (UTC) Received: from smtprelay.hostedemail.com (smtprelay0210.hostedemail.com [216.40.44.210]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 0020E12D for ; Wed, 22 Jul 2015 15:04:09 +0000 (UTC) Received: from smtprelay.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by smtpgrave06.hostedemail.com (Postfix) with ESMTP id 8BE92173867 for ; Wed, 22 Jul 2015 14:48:25 +0000 (UTC) Date: Wed, 22 Jul 2015 10:48:22 -0400 From: Steven Rostedt To: James Bottomley Message-ID: <20150722104822.2b749dc7@gandalf.local.home> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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, 22 Jul 2015 07:42:01 -0700 James Bottomley wrote: > 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. That may not be trivial. It would have to keep track of changes before the line, to match the line in previous commits. What happens if the line completely changes, or is in a complete rewrite of that code. I doubt it will be smart enough to follow a single line. Perhaps a range would be better? -- Steve