Community
Participate
Working Groups
Build Identifier: Build Id: 201101081000 eGit History does not show full history, does equivalent of "git log" not "git log --full-history" In the eGit history view, not all changes to a file are displayed. What the view shows is a equvalent of the command like "git log", it is somewhat misleadign because the actual history is reported on the gitweb portal through the equivalent of "git log --full-history". Another toggle could be super useful. Reproducible: Always Steps to Reproduce: 1. Right click on a file and go to history view 2. View the history and the versions displayed for the file 3. Compare it to "git log --full-history <filename>" on the command line Especially for early git users, it is confusing because they things git ate their commit.
Did you try the toggle "Show all branches" (right most button in History View) ?
Matthias, Thanks for your note. Yes, I did. It did not seem to change the view. BTW, is there an action log with commands or equivalents that eGit puts on disk I can review? We are just beginning to move to git and when our developers do not see all their changes in history, they seem to grow suspicious of both git and the plugin.
See [1] for detailed instructions. Please note that the user guide is also available in Eclipse help. The history view does not refresh by default, if you want that if auto-refreshes and follows selection click the toggle "Link with Selection", see [2]. Also note the filter buttons [3]. If you still miss something please specify in detail what you are missing. [1] http://wiki.eclipse.org/EGit/User_Guide#All_Branches [2] http://wiki.eclipse.org/EGit/User_Guide#Toolbar_actions [3] http://wiki.eclipse.org/EGit/User_Guide#Filter_settings
The problem you see could be that git does not show changes brought by merge commits. If a developer messes up during a merge and further modifies a file that was modified in one of the incoming branch of the merge, then this modification does not show up in git log. See https://groups.google.com/forum/#!msg/git-users/_02HNSG3Ft8/Nft9p8iG4SMJ and http://thread.gmane.org/gmane.comp.version-control.git/89400/focus=90659 I use "git whatchanged -m" to really see what changed in a commit, including "hidden" changes brought by merge commits. It would be nice if egit had an option to show such hidden changes!
eGit indeed cuts the display short; you can see it rendering the whole history, as the version relation graph lines continue all the way to the bottom of the view, but you can't scroll down to see more than certain amount of items. The workaround I used was to filter only the selected branch; this does not make the bug go away, but it reduces the amount of data, so the n items eGit displays took me farther away in time. However, it's a bit sad if you are looking at project that spans all the way to 2004 and you can even with tricks only see it back to 2012...
Jari, are you sure this is the same bug. In this bug it is found out that EGit is hiding certain commits (e.g. merge commits) when it is told to show the history of a single file. But the bug you found sounds more like EGit simply doesnt show too old commits. Like if there would be a maximum limit of commits shown and all older commits are not shown. If the bug you see is that EGit is not showing commits older than a certain commit (or: EGit is not showing more than <x> commits) then please open a new bug - that doesn't relate to this bug where only certain commits are not shown.
