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

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

From
David Turner <dturner@twopensource.com>
Date
Jul 9, 2015, 17:38 UTC
Message-ID
<1436463511.4542.27.camel@twopensource.com>
In-Reply-To
<xmqqegkhw8hf.fsf@gitster.dls.corp.google.com>

On Thu, 2015-07-09 at 10:23 -0700, Junio C Hamano wrote: <snip>

Show 16 quoted lines
> If I were David and sending this v4 patch, it would have looked like
> this.
>
> -- >8 --
> 
> From: David Turner <dturner@twopensource.com>
> Date: Tue, 7 Jul 2015 21:29:34 -0400
> Subject: [PATCH v4] log: add "log.follow" configuration variable
> 
> People who work on projects with mostly linear history with frequent
> whole file renames may want to always use "git log --follow" when
> inspecting the life of the content that live in a single path.
> 
> Teach the command to behave as if "--follow" was given from the
> command line when log.follow configuration variable is set *and*
> there is one (and only one) path on the command line.
Thanks.  That version is much better.
Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 7 in “log: add log.follow config option”
  1. log: add log.follow config optionDavid Turner, Jul 8, 2015
  2. Matthieu MoyJul 9, 2015
  3. Junio C HamanoJul 9, 2015
  4. David TurnerJul 9, 2015
  5. Junio C HamanoJul 9, 2015
  6. David TurnerJul 10, 2015
  7. Junio C HamanoJul 10, 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.