New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 746594 link

Starred by 3 users
Status: Fixed
Owner:
orodley@chromium.org
Closed: Jun 2018
Cc:
j...@chromium.org
flyboy@chromium.org
rauch+monorail-auto@google.com
█ orodley+autocc@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug
Git



Sign in to add a comment

Show something meaningful instead of commit hash in blame layer

Project Member Reported by altimin@chromium.org, Jul 19 2017 
Looking at the blame layer in the codesearch, it's rather hard to understand in which order the changes were made (and which are the latest changes). In internal google codesearch commits touching this file are numbered starting from 1 and this file-specific number is displayed.

I wonder if we can display something similar (or just showing commit time would be a great improvement).

Comment 1 by emso@chromium.org, Jul 28 2017

Labels: Git frontend
Status: Available (was: Untriaged)

Comment 2 by j...@chromium.org, May 16 2018

Owner: orodley@chromium.org
Status: Started (was: Available)

Comment 3 by j...@chromium.org, May 16 2018 

 Issue 694302  has been merged into this issue.

Comment 4 by orodley@chromium.org, May 24 2018

Status: Fixed (was: Started)
We now show the date at which each revision was committed in the blame layer.

Comment 5 by vitaliii@chromium.org, May 28 2018 

Is this already live?
I don't see any date, only an author and commit hash.
E.g. here https://cs.chromium.org/chromium/src/components/ntp_snippets/switches.h?q=he+file:%5Esrc/components/ntp_snippets/+package:%5Echromium$&dr=CSs&l=1.

Comment 6 by orodley@chromium.org, May 28 2018

Status: Assigned (was: Fixed)
Sorry, we had to roll this back because of  https://crbug.com/846368 . I'll update the bug again once we roll forward.

Comment 7 by orodley@chromium.org, Jun 14 2018

Status: Fixed (was: Assigned)
Rolled forward.
►

Sign in to add a comment