git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Sajine <euguess@gmail.com>
To: Jacob Helwig <jacob.helwig@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git log -M -- filename is not working?
Date: Fri, 7 May 2010 14:31:23 -0400	[thread overview]
Message-ID: <z2r76c5b8581005071131q15524cb8td6711dbb9142b28e@mail.gmail.com> (raw)
In-Reply-To: <h2m8c9a061005071110nf7e63220ked03598bfa66fbc9@mail.gmail.com>

On Fri, May 7, 2010 at 2:10 PM, Jacob Helwig <jacob.helwig@gmail.com> wrote:
> On Fri, May 7, 2010 at 11:07, Eugene Sajine <euguess@gmail.com> wrote:
>> Hi!
>>
>> I tried it in both git 1.6.5.6 and git 1.7.0.5
>>
>> The file has been moved:
>>
>> From
>> Src/folder1/folder2/File.java
>>
>> To src/main/java/folder1/folder2/File.java
>>
>> I don’t think it is relevant but just in case: The author has
>> committed the new file first, then the commit was amended with the
>> deletion of the source file.
>> So we ended up with the rename correctly detected.
>>
>> Now
>> $ git log –M -- src/main/java/folder1/folder2/File.java
>>
>> Shows only one last commit and doesn’t show the history when the file
>> was in source folder. Same thing happens with
>>
>> $ git log –C  -- src/main/java/folder1/folder2/File.java
>>
>> What gives?
>>
>> Thanks,
>> Eugene
>>
>
> 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??

Thanks,
Eugene

  reply	other threads:[~2010-05-07 18:31 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 [this message]
2010-05-07 18:37     ` Eli Barzilay
2010-05-07 20:25       ` Matthieu Moy
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  5:39           ` Junio C Hamano
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

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=z2r76c5b8581005071131q15524cb8td6711dbb9142b28e@mail.gmail.com \
    --to=euguess@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jacob.helwig@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).