follow file history across renames/etc...

[spearce]

Originally reported on Google Code with ID 68

example file:
https://chromium.googlesource.com/infra/infra.git/+log/8f1b4fe0782f6ef04f5519d615976148d5d4015a/appengine/chromium_status/appengine_module/chromium_status/status.py

this code has been moved around in the repo a couple of times which makes looking up
the history via gitiles kind of a pain.  would be nice if there were an option like
`git log --follow` where you could easily move back along the renames.

it doesn't need to fully populate the log by default ... i'd be happy if the last link
that series was something like:
  Renamed from <old file>
and <old file> was a link to the history at that commit

Reported by None on 2015-01-20 05:19:38

[spearce]

example file:
https://chromium.googlesource.com/infra/infra.git/+log/8f1b4fe0782f6ef04f5519d615976148d5d4015a/appengine/chromium_status/appengine_module/chromium_status/status.py

this code has been moved around in the repo a couple of times which makes looking up
the history via gitiles kind of a pain.  would be nice if there were an option like
`git log --follow` where you could easily move back along the renames.

it doesn't need to fully populate the log by default ... i'd be happy if the last link
that series was something like:
  Renamed from <old file>
and <old file> was a link to the history at that commit

Reported by None on 2015-01-20 05:19:38

[spearce]

Could this actually be the default behaviour? When do you not want to --follow?

Especially useful for chrome on android, as almost all our java code has been moved
around a couple times. Not having to go to command-line would be sooooo good.

Reported by None on 2015-06-24 14:36:32