From: Robert White <rjwhite2453@gmail.com>
To: git@vger.kernel.org
Subject: Confusing inconsistent option syntax
Date: Sun, 2 Dec 2018 21:07:47 +1100 [thread overview]
Message-ID: <20181202100747.GA5019@laptop> (raw)
`git log --pretty short` gives the error message "ambiguous argument
'short'". To get the expected result, you need to use `git log
--pretty=short`. However, `git log --since yesterday` and `git log
--since=yesterday` both work as expected.
When is an = needed? What is the reason for these inconsistencies?
---
Robert White
next reply other threads:[~2018-12-02 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 10:07 Robert White [this message]
2018-12-02 10:18 ` Confusing inconsistent option syntax Duy Nguyen
2018-12-03 22:14 ` 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=20181202100747.GA5019@laptop \
--to=rjwhite2453@gmail.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).