Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760287AbXJMA0R (ORCPT ); Fri, 12 Oct 2007 20:26:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752924AbXJMA0D (ORCPT ); Fri, 12 Oct 2007 20:26:03 -0400 Received: from mx1.redhat.com ([66.187.233.31]:37004 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752331AbXJMA0B (ORCPT ); Fri, 12 Oct 2007 20:26:01 -0400 Date: Fri, 12 Oct 2007 20:25:45 -0400 From: Dave Jones To: Linus Torvalds , Thomas Gleixner , Linux Kernel Subject: Re: arch merge fallout. Message-ID: <20071013002545.GB2383@redhat.com> Mail-Followup-To: Dave Jones , Linus Torvalds , Thomas Gleixner , Linux Kernel References: <20071012035743.GA12897@redhat.com> <20071012182504.GA9222@redhat.com> <20071012221253.GB4290@redhat.com> <20071012225222.GD4290@redhat.com> <20071013001153.GA30688@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071013001153.GA30688@redhat.com> User-Agent: Mutt/1.5.14 (2007-02-12) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1696 Lines: 51 On Fri, Oct 12, 2007 at 08:11:53PM -0400, Dave Jones wrote: > On Fri, Oct 12, 2007 at 04:14:54PM -0700, Linus Torvalds wrote: > > > > > > On Fri, 12 Oct 2007, Dave Jones wrote: > > > > > > Something I find useful is to just do for eg.. > > > > > > git log arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c > > > > > > from time to time, to figure out when certain changes happened, > > > or even to grep for something in a changelog. > > > With that file moved, git refuses to tell me about the log > > > of a file that doesn't exist, and the log of the moved > > > file in arch/x86 just has a single commit, detailing the move. > > > > > > Is there an easy way to get the complete log of a file? > > > > The "--follow" flag will follow renames when doing a log, so a simple > > > > git log --follow arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c > > > > will do it. > > Hrmm. > > $ git log --follow arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c > fatal: ambiguous argument 'arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c': > unknown revision or path not in the working tree. > Use '--' to separate paths from revisions > > Using --follow on the arch/x86 post-merge file gives me even less info > than it does without it :) duh. git log --stat --follow arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c works just fine. Thanks. (was running it on the old path) Dave -- http://www.codemonkey.org.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/