Re: Using "git log" to find the files patched at the same time as a named file

From: Zack Brown <zacharyb@gmail.com>
Date: Feb 3, 2010, 21:14 UTC
Message-ID: <218b69371002031314rb52da81k92c45f79dc6feca@mail.gmail.com>
In-Reply-To: <7vk4uughzf.fsf@alter.siamese.dyndns.org>

On Wed, Feb 3, 2010 at 3:52 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 9 quoted lines

> Zack Brown <zacharyb@gmail.com> writes:
>
>> If I have a filename I'm interested in, and I want to find other files
>> that have been modified in the same commits that modified the file I'm
>> interested in, how could I do that with git?
>
> Like this?
>
> $ git log --full-diff --name-status v1.6.0..master -- Makefile

Yes! Thank you!

I went back to the man page to see why I didn't find that before. Here's the text for the --full-diff option:

   "Without this flag, "git log -p <path>..." shows commits that touch
   the specified paths, and diffs about the same specified paths. With
   this, the full diff is shown for commits that touch the specified
   paths; this means that "<path>..." limits only commits, and doesn’t
   limit diff for those commits."

That's all the text that deals with --full-diff in the git log manpage. I'm not sure what it's trying to say - it seems really hard to understand. What about something like this:

"Without this flag, "git log -p <path>..." shows commits that touch the specified paths, but it only includes the diffs from those commits that affected those specified paths, regardless of whether other paths were changed in those same commits. With "git log --full-diff -p <path>...", git still only reports commits that touch the specified path, but now it also includes the diffs that affected any other paths changed in those same commits."

Would that be an improvement?

Be well, Zack

>
> to ask "Which files have changed in the commit that touch Makefile since
> v1.6.0 up to the tip of the master?"
>

-- 
Zack Brown