Bug 4655 - git log does not follow file renames correctly
Summary: git log does not follow file renames correctly
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Version Control ()
Version: Trunk
Hardware: PC Mac OS
: --- major
Target Milestone: ---
Assignee: Alan McGovern
Depends on:
Reported: 2012-04-25 18:53 UTC by Mikayla Hutchinson [MSFT]
Modified: 2012-04-27 14:02 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Mikayla Hutchinson [MSFT] 2012-04-25 18:53:26 UTC
The git log view's list of commits for a file tracks renames, i.e. shows the commits that affected the file when it had a different name. However, the diff list underneath is blank for these commits.

It looks like the log view is filtering the diff list to match the current filename. That doesn't just cause this bug, it's seriously misleading, because it makes it look like the commits only affected that file.

For an example, open FoldMarginMarker.cs in the MD sln and go down the list a few commits.
Comment 1 Alan McGovern 2012-04-27 14:02:29 UTC
This should be fixed now. I ported MonoDevelop to use some of the NGit utility classes directly which have greatly simplified this case.