Re: unexpected behavior with `git log --skip filename`

From: Jay Soffian <jaysoffian@gmail.com>
Date: Oct 7, 2011, 21:54 UTC
Message-ID: <CAG+J_DwnUOeDTiUW-UUJGLLg8jJ4EhXN21B7o_hOMnyowM9a8g@mail.gmail.com>
In-Reply-To: <20111007171503.GB16607@mcnabbs.org>

On Fri, Oct 7, 2011 at 1:15 PM, Andrew McNabb <amcnabb@mcnabbs.org> wrote:

Show 14 quoted lines

> 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".

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

j.