Skip to content

Clicking "History" should use --follow so we can have history even if files got moved/renamed.

Description

I'm in the process of evaluating GitLab to see if it suits the needs of our largish project. So far, so good. Outstanding work guys!

Since we're in the process of ditching autotools and go with CMake for every platform, a lot of file shuffling around is happening.

Problem: moving/renaming files "breaks" history. Well, it doesn't break it but I miss the reference to commits before the move/rename.

Proposal

Not knowing how your backend is handling "History" requests, I'm assuming it uses something like git log foo.bar and parses the info. If that's the case, could you guys turn that into git log --follow foo.bar?

Links / references

Please visit https://gitlab.com/h.udo/xbmc/commits/master/project/cmake/scripts/common/PrepareEnv.cmake and you'll notice commit history stops at [cmake] Rename script/common/ files, the commit that renamed/moved files.

Thx!