From: David Symonds Date: Wed, 07 Nov 2007 23:00:42 GMT Subject: Re: Inconsistencies with git log Message-ID: In-Reply-To: <9e4733910711071445p7cfb6cffx83adb1d84d6bf9d8@mail.gmail.com> On Nov 8, 2007 9:45 AM, Jon Smirl wrote: > On 11/7/07, Johannes Schindelin wrote: > > Hi, > > > > On Wed, 7 Nov 2007, Jon Smirl wrote: > > > > > In project root: > > > git log arch/powerpc/platforms/52xx > > > works as expected > > > > > > cd arch/powerpc/platforms/52xx > > > git log arch/powerpc/platforms/52xx > > > fatal: ambiguous argument 'arch/powerpc/platforms/52xx': unknown > > > revision or path not in the working tree. > > > Use '--' to separate paths from revisions > > > > Try "git log ." > > Shouldn't git log default to "git log ."? It might be nice if it did, but since Git tracks whole *trees* (not files) then it makes more sense to show the log of the repository in its default mode. On the other hand, it'd sure be nice if git-status would show relative paths when you're in subdirectories, especially when you're in a deeply nested directory hierarchy. It's a lot easier to see that "foo.txt" and "../bar.txt" have modifications. Furthermore, it is the relative path that you have to pass to git-add anyway, so quick copy-n-pasting from git-status output often doesn't work. Dave.