git/list[1] front-page[2] threads[3] people[4] search[5] about
 

unexpected behavior with `git log --skip filename`

From
AMAndrew McNabb <amcnabb@mcnabbs.org>
Date
Oct 7, 2011, 17:15 UTC
Message-ID
<20111007171503.GB16607@mcnabbs.org>

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

Next: Jay Soffian
Message 1 of 4 in “unexpected behavior with `git log --skip filename`”
  1. Andrew McNabbOct 7, 2011
  2. Jay SoffianOct 7, 2011
  3. Andrew McNabbOct 8, 2011
  4. Jay SoffianOct 8, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.