Re: Inconsistencies with git log

From: Jon Smirl <jonsmirl@gmail.com>
Date: Nov 8, 2007, 00:09 UTC
Message-ID: <9e4733910711071609t3e5412f1mf02e501b2d820bb3@mail.gmail.com>
In-Reply-To: <Pine.LNX.4.64.0711080003080.4362@racer.site>

On 11/7/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

> It is consistent, when you realise that the path arguments are interpreted
> relative to the project root.

Then why doesn't this work?

jonsmirl@terra:~/mpc5200b$ git log Documentation all the log for Documentation.... jonsmirl@terra:~/mpc5200b$ cd Documentation jonsmirl@terra:~/mpc5200b/Documentation$ git log Documentation fatal: ambiguous argument 'Documentation': unknown revision or path not in the working tree. Use '--' to separate paths from revisions jonsmirl@terra:~/mpc5200b/Documentation$

Show 5 quoted lines

>
> Hth,
> Dscho
>
>

-- 
Jon Smirl
jonsmirl@gmail.com

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.