Re: Inconsistencies with git log

From: Jakub Narebski <jnareb@gmail.com>
Date: Nov 9, 2007, 17:41 UTC
Message-ID: <fh263e$6c0$1@ger.gmane.org>
In-Reply-To: <9e4733910711090920m6b0b7704x7c5a3849215f385c@mail.gmail.com>

Jon Smirl wrote:

> The summary of this is that new users do not expect "git log" to give
> them the whole log when the command is executed in a subdirectory.
> This causes a training burden because of the unexpected behavior. They
> try 'git log' and then I have to tell them to use "git log ."

That's too bad, that they have to unlearn bad expectations. Having "git log" _always_ meaning whole history is very useful. You can always do "git log ." (two characters more); how do you propose to request full history from within subdirectory if by default "git log" output would limit history to current directory only?

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

$ 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.