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

Issue 611870 link

Starred by 2 users
Status: Duplicate
Owner:
█ kateso...@chromium.org
Last visit > 30 days ago
Closed: Aug 2016
Cc:
jchin...@chromium.org
█ mimee@chromium.org
█ iannucci@chromium.org
█ mmand...@chromium.org
mbarbe...@chromium.org
infe...@chromium.org
█ robert...@chromium.org
chanli@chromium.org
lijeffrey@chromium.org
liaoyuke@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Make Gitiles support git-blame on case-insensitive file paths?

Project Member Reported by st...@chromium.org, May 13 2016 
Now for Chrome crashes on Windows, the file paths are lowercase in Chrome symbol. When run git-blame with such lowercase, Findit got 404.

Assign to katesonia@ to follow up for the possibility.

Comment 1 by kateso...@chromium.org, May 13 2016

Cc: iannucci@chromium.org
Labels: OS-Windows
Here is one sample: https://crash.corp.google.com/browse?stbtiq=426bcc0a00000000

The original file path should be: third_party/WebKit/Source/core/paint/PaintLayerClipper.cpp,
Instead, the file path in Chrome symbol is:
third_party/webkit/source/core/paint/paintlayerclipper.cpp

Right now, Gitiles only supports "original" file path. So for those lower file paths, people will get 404s when running git-blames.

Hi, @iannucci, is it possible that we can make gitile support file path matching ignoring case? This can solve findit problem in Chrome canary/win crashes and SyzyASan jobs in CF. Besides, this will also benefit crash, since they are doing some very hacky thing to work around this.

Comment 2 by kateso...@chromium.org, Aug 18 2016

Mergedinto: 611810
Status: Duplicate (was: Assigned)
►

Sign in to add a comment