git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: log: option "--follow" not the default for a single file?

From
Jeff King <peff@peff.net>
Date
Dec 1, 2011, 18:52 UTC
Message-ID
<20111201185230.GB2873@sigill.intra.peff.net>
In-Reply-To
<CAN0XMOJGm1frOi7FEke7LfHCSBt2DRn_npkdKe0m3qZ=hQPNHw@mail.gmail.com>
On Wed, Nov 30, 2011 at 07:38:23PM +0100, Ralf Thielow wrote:
> >     pathspec. That may happen to match a single file in the current
> >     revision, but to git it is actually a prefix-limiting pattern, and
> Is it possible to detect the case of a single file in the current
> revisionand use "--follow" by default for exactly that?

It's possible, but it is changing the meaning of "git log foo". With the current code, even if "foo" is currently a file, it will match "foo/bar" in a prior revision. Switching this to "--follow" will not.

-Peff
Previous: Ralf ThielowNext: Ralf Thielow
Message 5 of 7 in “log: option "--follow" not the default for a single file?”
  1. Ralf ThielowNov 29, 2011
  2. Jeff KingNov 30, 2011
  3. Junio C HamanoNov 30, 2011
  4. Ralf ThielowNov 30, 2011
  5. Jeff KingDec 1, 2011
  6. Ralf ThielowDec 1, 2011
  7. Jeff KingDec 1, 2011

Read the whole thread, see it on lore, or plain text.

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