Community
Participate
Working Groups
The History view shows the author date. This is not very helpful to track what happened in a branch. More interesting for that would be the submitted-at date. See attached picture to see the confusion.
Created attachment 209728 [details] Picture of History view
+1. The author date is only interesting for archeology, but the commit date is what determines the state of the repository.
Proposed fix pushed to https://git.eclipse.org/r/#/c/5165/
merged as 9066219c8c172cf1696ddffc6e8ac15a70e4cb07
Thanks Kevin and Matthias! Verified in 2.0.0.201202261814.
While writing another comment in bug 372637 I realized that my original enhancement request is not fixed: the fix shows the COMMITTER date but what I'm really interested in is the date and the person who pushed the commit into the shared/live repository i.e. the real committer with the appropriate permission. In Git speech this is the submitted-by and submitted-at information.
If bug 372637 would get fixed by Gerrit, then I guess I could live with the current solution.
We could make those two columns either optional or depending on whether Gerrit is configured on the repository.
If a change went through Gerrit and Gerrit review note is available we could display the following additional information from the review note as additional optional columns in the history view: - Submitted-at - Submitted-by and maybe also the review votings (the voting categories are configurable on the Gerrit server) - Code-Review+2 - Verified+1
(In reply to comment #9) > If a change went through Gerrit and Gerrit review note is available we could > display the following additional information from the review note as additional > optional columns in the history view: > - Submitted-at > - Submitted-by > and maybe also the review votings (the voting categories are configurable on > the Gerrit server) > - Code-Review+2 > - Verified+1 +1, but it should be possible to choose each optional column individually, otherwise I'd only want Submitted-at and Submitted-by.
*** Bug 372637 has been marked as a duplicate of this bug. ***