Bug 3108 - Git log on single file should use --follow to track renames of that file
Summary: Git log on single file should use --follow to track renames of that file
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Version Control ()
Version: 2.8.5
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Alan McGovern
URL:
Depends on:
Blocks:
 
Reported: 2012-01-27 05:31 UTC by Nicklas Overgaard
Modified: 2012-02-08 09:52 UTC (History)
1 user (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Nicklas Overgaard 2012-01-27 05:31:33 UTC
As the summary says..

I'm currently on a project where we moved a lot of files recently - files which has a lot of history.

However, the only thing the logviewer shows for these files now is the rename commit. Git supports viewing logs of the entire file, accross renames - on the commandline by using the --follow parameter.

Would it be possible to get monodevelop to do the same?
Comment 1 Alan McGovern 2012-02-05 20:33:26 UTC
This has just been implemented should be in the next release of MonoDevelop. Thanks for reporting the issue, it was simply an oversight that it was not done.
Comment 2 Nicklas Overgaard 2012-02-08 09:52:04 UTC
Nice, thanks! :)