Christian CouderHi,
At GitLab, we are annoyed by the fact that `git log` doesn't seem to work well when using it with both --follow and --skip.
For example:
> git log --oneline -6 README.md
a299e3a README.md: format CLI commands with code syntax c9a014e README.md: don't take 'commandname' literally a217f07 README.md: move down historical explanation about the name 28513c4 README.md: don't call git stupid in the title d9b297d README.md: move the link to git-scm.com up 6164972 README.md: add hyperlinks on filenames
> git log --skip 2 --oneline -6 README.md
a217f07 README.md: move down historical explanation about the name 28513c4 README.md: don't call git stupid in the title d9b297d README.md: move the link to git-scm.com up 6164972 README.md: add hyperlinks on filenames 4ad21f5 README: use markdown syntax
The above 2 commands seem to work well, but:
> git log --follow --skip 2 --oneline -6 README.md
a299e3a README.md: format CLI commands with code syntax c9a014e README.md: don't take 'commandname' literally a217f07 README.md: move down historical explanation about the name 28513c4 README.md: don't call git stupid in the title d9b297d README.md: move the link to git-scm.com up 6164972 README.md: add hyperlinks on filenames
So with --follow it looks like the top 2 commits are not skipped any more.
Thanks, Christian.