All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Turner <dturner@twopensource.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>, git@vger.kernel.org
Subject: Re: [PATCH v4] log: add log.follow config option
Date: Thu, 09 Jul 2015 13:38:31 -0400	[thread overview]
Message-ID: <1436463511.4542.27.camel@twopensource.com> (raw)
In-Reply-To: <xmqqegkhw8hf.fsf@gitster.dls.corp.google.com>

On Thu, 2015-07-09 at 10:23 -0700, Junio C Hamano wrote:
<snip>
> 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.

  reply	other threads:[~2015-07-09 17:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 17:42 [PATCH v4] log: add log.follow config option David Turner
2015-07-09  8:38 ` Matthieu Moy
2015-07-09 17:23   ` Junio C Hamano
2015-07-09 17:38     ` David Turner [this message]
2015-07-09 17:58       ` Junio C Hamano
2015-07-10 17:53         ` David Turner
2015-07-10 21:03           ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1436463511.4542.27.camel@twopensource.com \
    --to=dturner@twopensource.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.