search

jonnyjjgarza / gitiles

Automatically exported from code.google.com/p/gitiles
1 stars 0 forks source link

follow file history across renames/etc... #68

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
example file:
https://chromium.googlesource.com/infra/infra.git/+log/8f1b4fe0782f6ef04f5519d61
5976148d5d4015a/appengine/chromium_status/appengine_module/chromium_status/statu
s.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

Original issue reported on code.google.com by vapier@chromium.org on 20 Jan 2015 at 1:19

GoogleCodeExporter commented 9 years ago 
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.

Original comment by wn...@chromium.org on 24 Jun 2015 at 9:36