The "--skip" option to "git log" did not behave as I expected, but I'm not sure whether this was user error, unclear documentation, or a bug. Specifically, I ran the following, intending to find the previous revision of a given file: git log --skip=1 -n 1 --oneline some-filename My expectation was that this would behave the same as: git log -n 2 --oneline some-filename |tail -n 1 Instead, the --skip=1 parameter seemed to be ignored. After I tried several different values, it appears that the commits are skipped before path matching with "some-filename". Is this the intended behavior? If so, should the documentation be clarified by changing "Note that they are applied before commit ordering and formatting options, such as --reverse" to something like "Note that they are applied before path matching, commit ordering, and formatting options, such as --reverse"? -- Andrew McNabb http://www.mcnabbs.org/andrew/ PGP Fingerprint: 8A17 B57C 6879 1863 DE55 8012 AB4D 6098 8826 6868 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html