From mboxrd@z Thu Jan  1 00:00:00 1970
From: Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: git mv (was Re: [git pull] ACPI & Suspend patches for
 2.6.29-rc0)
Date: Fri, 9 Jan 2009 13:58:43 -0800 (PST)
Message-ID: <alpine.LFD.2.00.0901091357460.6528@localhost.localdomain>
References: <alpine.LFD.2.00.0901090550590.4091@localhost.localdomain>  <alpine.LFD.2.00.0901091200150.6528@localhost.localdomain>  <alpine.LFD.2.00.0901091537530.16697@localhost.localdomain>  <alpine.LFD.2.00.0901091305160.6528@localhost.localdomain>
 <20090109212757.GA25434@uranus.ravnborg.org> <1231537636.5726.4.camel@brick>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Return-path: <linux-acpi-owner@vger.kernel.org>
In-Reply-To: <1231537636.5726.4.camel@brick>
Sender: linux-acpi-owner@vger.kernel.org
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>, Len Brown <lenb@kernel.org>, Andrew Morton <akpm@linux-foundation.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, linux-acpi@vger.kernel.org, Linux Power Management List <linux-pm@lists.osdl.org>
List-Id: linux-pm@vger.kernel.org



On Fri, 9 Jan 2009, Harvey Harrison wrote:
>
> In that specific case you could just do:
> 
> gitk -- name1 name2
> 
> And that might be closer to what you're looking for.

yes. If you know the names you are interested in (and using "--follow" may 
be a way to do that), then just naming them explicitly is likely the right 
thing, because then you get the whole nice git ability to follow different 
cases across merges etc.

			Linus