On 11/7/07, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > Hi, > > On Wed, 7 Nov 2007, Jon Smirl wrote: > > > On 11/7/07, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > > > > > We also tend to take the approach of viewing the history as that of > > > the whole project. > > > > But if you type 'git log' while cd'd into a subdirectory the whole log > > is almost never what you want. It's this kind of thing that makes git > > harder to use. > > When I am working in a subdirectory, I often want the whole history. For > example, when I am working on the documentation, sometimes I need to look > up a commit real quick, that touched other parts. > > Besides, adding a space and a dot is not what qualifies for "harder to > use" with this developer. So if git log is always whole tree, why doesn't this work? 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 It's not consistent. git log with no parameters is relative to the project root, git log with a parameter is relative to the current directory. -- Jon Smirl jonsmirl@xxxxxxxxx - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
