* [BUG?] git log with --follow and --skip
@ 2016-10-06 20:24 Christian Couder
0 siblings, 0 replies; only message in thread
From: Christian Couder @ 2016-10-06 20:24 UTC (permalink / raw)
To: git
Hi,
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-10-06 20:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-10-06 20:24 [BUG?] git log with --follow and --skip Christian Couder
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.