On Fri, Oct 07, 2011 at 05:54:36PM -0400, Jay Soffian wrote: > > Hmm: > > $ git log --oneline GIT-VERSION-GEN | head -2 > 7f41b6bbe3 Post 1.7.7 first wave > 703f05ad58 Git 1.7.7 > > $ git log --oneline --skip=1 -n 1 GIT-VERSION-GEN > 703f05ad58 Git 1.7.7 I went back to reproduce this, and I think I may have been using the --follow option earlier. In my private repository, git log gives identical output for the last two commits when I don't specify --skip: $ git log -n 2 --oneline httpd.conf.orig f0026e9 updated many of the *.orig files to the latest version e57e840 moved the .orig files into place, too $ git log --follow -n 2 --oneline httpd.conf.orig f0026e9 updated many of the *.orig files to the latest version e57e840 moved the .orig files into place, too $ But when I specify --skip=1, the output is different: $ git log -n 1 --skip=1 --oneline httpd.conf.orig e57e840 moved the .orig files into place, too $ git log --follow -n 1 --skip=1 --oneline httpd.conf.orig f0026e9 updated many of the *.orig files to the latest version $ GIT-VERSION-GEN example that you shared, I don't notice this difference. It's not immediately obvious to me what's different between the two examples. -- 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