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

Re: [PATCH] log: add log.follow config option

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 1, 2015, 21:19 UTC
Message-ID
<xmqqvbe37eyy.fsf@gitster.dls.corp.google.com>
In-Reply-To
<vpq8uazo9y6.fsf@anie.imag.fr>
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
Show 8 quoted lines
> So activating --follow for all "git log" calls would prevent log from
> being used with several pathspecs.
>
> Or, do you have a preparation patch that allows --follow with multiple
> pathspecs? ;-)
>
> In any case, you have to test "git log -- path1 path2" with the option
> activated.
Or more commonly, just "git log" with no pathspec.

I also think that it is a bad idea to force "log --follow" to people before it is made into a true feature; as it stands, it is merely a "checkbox" item. It has too severe limitation to be used seriously in real projects, unless your history is completely linear.

cf.
  http://thread.gmane.org/gmane.comp.version-control.git/269357/focus=269433
Previous: Matthieu MoyNext: David Turner
Message 3 of 6 in “log: add log.follow config option”
  1. log: add log.follow config optionDavid Turner, Jul 1, 2015
  2. Matthieu MoyJul 1, 2015
  3. Junio C HamanoJul 1, 2015
  4. David TurnerJul 2, 2015
  5. Matthieu MoyJul 3, 2015
  6. Junio C HamanoJul 3, 2015

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.