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 A440D273 for ; Wed, 22 Jul 2015 15:41:08 +0000 (UTC) Received: from bedivere.hansenpartnership.com (bedivere.hansenpartnership.com [66.63.167.143]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 23C1212F for ; Wed, 22 Jul 2015 15:41:08 +0000 (UTC) Message-ID: <1437579665.2171.21.camel@HansenPartnership.com> From: James Bottomley To: Steven Rostedt Date: Wed, 22 Jul 2015 08:41:05 -0700 In-Reply-To: <20150722104822.2b749dc7@gandalf.local.home> 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> <20150722104822.2b749dc7@gandalf.local.home> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: Dan Carpenter , ksummit-discuss@lists.linuxfoundation.org, 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 10:48 -0400, Steven Rostedt wrote: > 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? I assume you missed the follow up? It does exist: git log -L It will follow a single line, a line range or a regex delimited search set. James