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 3, 2015, 17:47 UTC
Message-ID
<xmqqy4ix3zh8.fsf@gitster.dls.corp.google.com>
In-Reply-To
<vpqr3op676u.fsf@anie.imag.fr>
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
Show 11 quoted lines
> David Turner <dturner@twopensource.com> writes:
>
>> Twitter's history is almost completely linear, so it's useful for us.  
>>
>> Since it looks like the patch won't be useful outside of our context,
>> I'll just rewrite it to check the pathspec count, and not upstream it
>> until follow becomes more general.
>
> As long as it's an opt-in and that the documentation states the
> limitations clearly enough, I think it makes sense to me to have this
> upstream.

Perhaps. But at least "log -- 1 2" and "log --" should not be broken for those that set the configuration.

Unless you are counting these as also "limitations", that is.
Previous: Matthieu Moy
Message 6 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.