From: Jakub Narebski <jnareb@gmail.com>
To: Mike Hommey <mh@glandium.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Jari Aalto <jari.aalto@cante.net>,
git@vger.kernel.org
Subject: Re: [PATCH] git-rebase.sh: Update USAGE string (No. 1)
Date: Mon, 4 Feb 2008 13:53:23 +0100 [thread overview]
Message-ID: <200802041353.25592.jnareb@gmail.com> (raw)
In-Reply-To: <20080204115741.GA23834@glandium.org>
On Mon, 4 Feb 2008, Mike Hommey wrote:
> On Mon, Feb 04, 2008 at 11:15:20AM +0100, Jakub Narebski <jnareb@gmail.com> wrote:
>> Junio C Hamano wrote:
>>> Unfortunately, the majority of, if not all of, our existing
>>> documents use () instead for that purpose.
>>>
>>> So pros-and-cons are that [...] (2) our use of (), as we
>>> consistently use them, does not hurt readability (neutral); and
The above was re-added by me.
>> Actually we are not entirely consistent here. git-init(1) has
>> --shared[={false|true|umask|group|all|world|everybody}]
>> in the option description, git-rev-list(1) has
>> [ --date={local|relative|default|iso|rfc|short} ]
>
> What is inconsistent here ? The first tells you you can use --shared without
> an argument. And it's [--shared[=<permissions>]] in the synopsis, so you
> may omit --shared, or use in alone, or specify permissions. The second tells
> you can't use --date without an additional argument.
You have cut a bit too much when quoting. The inconsistency is between
git-branch(1) using () to delimit mutually exclusive options:
git-branch (-m | -M) [<oldbranch>] <newbranch>
and git-init(1) (and git-rev-list(1)) using {} for that:
--shared[={false|true|umask|group|all|world|everybody}]
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-02-04 12:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 20:19 [PATCH] git-rebase.sh: Update USAGE string Jari Aalto
2008-02-03 21:14 ` Jakub Narebski
2008-02-03 23:33 ` [PATCH] git-rebase.sh: Update USAGE string (No. 1) Jari Aalto
2008-02-03 23:41 ` Johannes Schindelin
2008-02-03 23:52 ` Jakub Narebski
2008-02-04 0:11 ` Jari Aalto
2008-02-04 0:27 ` Johannes Schindelin
2008-02-04 0:39 ` Junio C Hamano
2008-02-04 10:15 ` Jakub Narebski
2008-02-04 11:57 ` Mike Hommey
2008-02-04 12:53 ` Jakub Narebski [this message]
2008-02-04 0:24 ` Junio C Hamano
2008-02-04 8:04 ` [PATCH v3] git-rebase.sh: Update USAGE string Jari Aalto
2008-02-04 11:12 ` [PATCH] git-rebase.sh: Update USAGE string (No. 1) しらいしななこ
2008-02-04 15:06 ` rebase -i and --whitespace, was " Johannes Schindelin
2008-02-04 15:42 ` Jakub Narebski
2008-02-04 16:32 ` Johannes Schindelin
2008-02-05 23:43 ` Junio C Hamano
2008-02-06 1:00 ` Johannes Schindelin
2008-02-04 0:16 ` [PATCH v2] git-rebase.sh: Update USAGE string Jari Aalto
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=200802041353.25592.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jari.aalto@cante.net \
--cc=mh@glandium.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).