From: Francis Irving <francis@scraperwiki.com>
To: git@vger.kernel.org
Subject: Documentation for "git log --all" incorrect
Date: Wed, 29 Oct 2014 11:51:34 +0000 [thread overview]
Message-ID: <20141029115134.GA33348@bat.dot-bit.org> (raw)
The help for "git log --all" says:
--all
Pretend as if all the refs in refs/ are listed on
the command line as <commit>.
This makes no sense, as <commit> is not a documented valid command line
parameter. These are the documented parameters:
SYNOPSIS
git log [<options>] [<revision range>] [[--] <path>...]
Even if it means <revision range>, which is my best guess, it still
makes no sense as <revision range> cannot be a list of many refs.
I suspect both the documentation for "--all" and the documentation for
the basic options are either incorrect, or confusing by using multiple
names for the same thing.
I'm using git 1.9.2
Francis
next reply other threads:[~2014-10-29 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 11:51 Francis Irving [this message]
2014-10-29 19:54 ` Documentation for "git log --all" incorrect Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141029115134.GA33348@bat.dot-bit.org \
--to=francis@scraperwiki.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).