{"thread":{"id":"5497","subject":"git-rev-list --full-history --parents doesn't respect path limit and shows all merges","startedAt":"2006-09-06T11:11:12Z","lastAt":"2006-09-06T11:11:12Z","messageCount":1,"participants":["Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"26398","messageId":"edmabt$3tc$1@sea.gmane.org","threadId":"5497","inReplyTo":null,"subject":"git-rev-list --full-history --parents doesn't respect path limit and shows all merges","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2006-09-06T11:11:12Z","receivedAt":"2006-09-06T11:11:12Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"When trying to speed-up gitweb by using only one git-rev-list invocation to\nget _parsed_ list of revisions, and not first call git-rev-list to get list\nof revisions, and then for each revision call git-rev-list --max-count=1\n--parennts --header to parse a commit, I have encountered the following\nerror in (most probably) --full-history implementation.\n\nNamely the following work as expected, returning only one commit:\n\n  git rev-list HEAD -- gitweb/git-logo.png\n  git rev-list HEAD --full-history -- gitweb/git-logo.png\n  git rev-list HEAD --parents -- gitweb/git-logo.png\n \nbut the following command\n\n  git rev-list HEAD --full-history --parents -- gitweb/git-logo.png\n\nreturns additionally _all_ the merges.\n\n\nI don't know if it is a feature or a bug (I think that is the latter),\nbut it seriously screw mentioned plan to make gitweb faster a bit.\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"}]}