public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
To: Eli Barzilay <eli@barzilay•org>
Cc: Eugene Sajine <euguess@gmail•com>,
	Jacob Helwig <jacob.helwig@gmail•com>,
	git@vger•kernel.org
Subject: Re: Re: git log -M -- filename is not working?
Date: Fri, 07 May 2010 22:25:35 +0200	[thread overview]
Message-ID: <vpqfx23wjb4.fsf@bauges.imag.fr> (raw)
In-Reply-To: <19428.24021.324557.517627@winooski.ccs.neu.edu> (Eli Barzilay's message of "Fri\, 7 May 2010 14\:37\:09 -0400")

Eli Barzilay <eli@barzilay•org> writes:

> On May  7, Eugene Sajine wrote:
>> On Fri, May 7, 2010 at 2:10 PM, Jacob Helwig <jacob.helwig@gmail•com> wrote:
>> > You want the --follow flag, too.
>> 
>> Thanks! I missed this guy. By the way it seems that --follow flag
>> works without -M or -C.
>> 
>> Are those deprecated or I'm missing the difference between three of
>> them??
>
> BTW, I've had at least 4 people now who got confused by this.  Is
> there any use for -M/-C without --follow?  In any case, it will be
> very helpful if the -M/-C descriptions said "see also --follow".
>
> Also, is there a way to set this as the default for `git log'?

I guess -M and -C are here because log accepts all options that diff
accepts, in case you run "git log -p". Then, -M and -C control what
diff is displayed to the user.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  reply	other threads:[~2010-05-07 20:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07 18:07 git log -M -- filename is not working? Eugene Sajine
2010-05-07 18:10 ` Jacob Helwig
2010-05-07 18:31   ` Eugene Sajine
2010-05-07 18:37     ` Eli Barzilay
2010-05-07 20:25       ` Matthieu Moy [this message]
2010-05-07 20:28       ` Jakub Narebski
2010-05-08  4:44       ` Jeff King
2010-05-08  5:12         ` Eli Barzilay
2010-05-08  5:30           ` Jeff King
2010-05-08  7:08             ` Eli Barzilay
2010-05-12 11:38               ` Jeff King
2010-05-12 12:01                 ` Eli Barzilay
2010-05-12 12:49                   ` Jeff King
2010-05-12 13:03                     ` Jeff King
2010-05-12 14:35                     ` Eli Barzilay
2010-05-12 16:07                       ` Bo Yang
2010-05-12 16:45                         ` Jeff King
2010-05-13  2:12                           ` Bo Yang
2010-05-13  4:39                             ` Eli Barzilay
2010-05-14  4:55                       ` Jeff King
2010-05-14  5:05                         ` Eli Barzilay
2010-05-12 13:06                   ` Bo Yang
2010-05-12 13:09                     ` Jeff King
2010-05-12 14:42                     ` Eli Barzilay
2010-05-12 14:49                       ` Bo Yang
2010-05-08  5:39           ` 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=vpqfx23wjb4.fsf@bauges.imag.fr \
    --to=matthieu.moy@grenoble-inp$(echo .)fr \
    --cc=eli@barzilay$(echo .)org \
    --cc=euguess@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=jacob.helwig@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox