All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: David Turner <dturner@twopensource.com>, git@vger.kernel.org
Subject: Re: [PATCH] log: add log.follow config option
Date: Wed, 01 Jul 2015 14:19:49 -0700	[thread overview]
Message-ID: <xmqqvbe37eyy.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <vpq8uazo9y6.fsf@anie.imag.fr> (Matthieu Moy's message of "Wed, 01 Jul 2015 23:16:17 +0200")

Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:

> 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

  reply	other threads:[~2015-07-01 21:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 19:03 [PATCH] log: add log.follow config option David Turner
2015-07-01 21:16 ` Matthieu Moy
2015-07-01 21:19   ` Junio C Hamano [this message]
2015-07-02 18:43     ` David Turner
2015-07-03  7:17       ` Matthieu Moy
2015-07-03 17:47         ` 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=xmqqvbe37eyy.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=dturner@twopensource.com \
    --cc=git@vger.kernel.org \
    /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.