{"thread":{"id":"37830","subject":"Documentation for \"git log --all\" incorrect","startedAt":"2014-10-29T11:51:34Z","lastAt":"2014-10-29T19:54:45Z","messageCount":2,"participants":["Francis Irving","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"251174","messageId":"20141029115134.GA33348@bat.dot-bit.org","threadId":"37830","inReplyTo":null,"subject":"Documentation for \"git log --all\" incorrect","fromName":"Francis Irving","fromEmail":"francis@scraperwiki.com","sentAt":"2014-10-29T11:51:34Z","receivedAt":"2014-10-29T11:51:34Z","isPatch":false,"sender":{"key":"francis@scraperwiki.com","avatar":null},"body":"The help for \"git log --all\" says:\n\n       --all\n                  Pretend as if all the refs in refs/ are listed on\n                  the command line as <commit>.\n\nThis makes no sense, as <commit> is not a documented valid command line\nparameter. These are the documented parameters:\n\n        SYNOPSIS\n               git log [<options>] [<revision range>] [[--] <path>...]\n\nEven if it means <revision range>, which is my best guess, it still\nmakes no sense as <revision range> cannot be a list of many refs.\n\nI suspect both the documentation for \"--all\" and the documentation for\nthe basic options are either incorrect, or confusing by using multiple\nnames for the same thing.\n\nI'm using git 1.9.2\n\nFrancis\n"},{"id":"251193","messageId":"20141029195445.GA27413@peff.net","threadId":"37830","inReplyTo":"20141029115134.GA33348@bat.dot-bit.org","subject":"Re: Documentation for \"git log --all\" incorrect","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2014-10-29T19:54:45Z","receivedAt":"2014-10-29T19:54:45Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Oct 29, 2014 at 11:51:34AM +0000, Francis Irving wrote:\n\n> The help for \"git log --all\" says:\n> \n>        --all\n>                   Pretend as if all the refs in refs/ are listed on\n>                   the command line as <commit>.\n> \n> This makes no sense, as <commit> is not a documented valid command line\n> parameter. These are the documented parameters:\n> \n>         SYNOPSIS\n>                git log [<options>] [<revision range>] [[--] <path>...]\n> \n> Even if it means <revision range>, which is my best guess, it still\n> makes no sense as <revision range> cannot be a list of many refs.\n\nThe text for \"--all\" comes from rev-list-options.txt, which is included\nin git-rev-list.txt and git-log.txt. It makes sense in the former but\nnot the latter. One fix would be to use \"<commit>\" in the synopsis for\ngit-log. But I think it would probably be OK to just drop the \"as\n<commit>\" part of the --all text (and other related options need this,\ntoo). It seems pretty clear to me without it.\n\nDo you want to try your hand at a patch?\n\n-Peff\n"}]}