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

git-rev-list --full-history --parents doesn't respect path limit and shows all merges

From
Jakub Narebski <jnareb@gmail.com>
Date
Sep 6, 2006, 11:11 UTC
Message-ID
<edmabt$3tc$1@sea.gmane.org>

When trying to speed-up gitweb by using only one git-rev-list invocation to get _parsed_ list of revisions, and not first call git-rev-list to get list of revisions, and then for each revision call git-rev-list --max-count=1 --parennts --header to parse a commit, I have encountered the following error in (most probably) --full-history implementation.

Namely the following work as expected, returning only one commit:
  git rev-list HEAD -- gitweb/git-logo.png
  git rev-list HEAD --full-history -- gitweb/git-logo.png
  git rev-list HEAD --parents -- gitweb/git-logo.png
 
but the following command
  git rev-list HEAD --full-history --parents -- gitweb/git-logo.png
returns additionally _all_ the merges.

I don't know if it is a feature or a bug (I think that is the latter), but it seriously screw mentioned plan to make gitweb faster a bit.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Message 1 of 1 in “git-rev-list --full-history --parents doesn't respect path limit and shows all merges”
  1. Jakub NarebskiSep 6, 2006

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.