Re: arch merge fallout.

[Linus Torvalds <torvalds@linux-foundation.org>]

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.

[ Although I actually introduced a bug in that last week, so if it gives 
  empty output for you, add a "--stat" to get a diffstat (or "-p" to get 
  the whole patch) to work around a stupid mistake. That bug is in both 
  1.5.3.3 and 1.5.3.4 - and Junio happens to be away for two weeks, so 
  it's not fixed in any release yet. I have a trivial patch for it if you 
  care, but the "use -p" workaround is usually what you want to do anyway, 
  which is probably why  nobody even noticed it was broken! ]

			Linus