From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Paul Bolle <pebolle@tiscali.nl>,
Nicolas Sebrecht <nicolas.s.dev@gmx.fr>,
git@vger.kernel.org
Subject: [PATCH] Re: [TRIVIAL] Documentation: merge: one <remote> is required
Date: Wed, 12 Aug 2009 15:29:24 +0200 [thread overview]
Message-ID: <20090812132924.GA28345@vidovic> (raw)
In-Reply-To: <m31vnhpc5v.fsf@localhost.localdomain>
The 12/08/09, Jakub Narebski wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
> > After you brought up this "one or more", I re-read the docs your patches
> > touched, thinking that the author might have meant 'zero or more of A'
> > with these '<A>...' notation.
> >
> > And I realized that they made perfect sense.
This was my initial thought but...
> I would have thought that it makes more sense to have
>
> <something>...
>
> for one or more, and
>
> [<something>... ]
>
> for zero or more (optional one or more).
...their sense is what Posix states:
Ellipses ( "..." ) are used to denote that one or more occurrences of an
operand are allowed. When an option or an operand followed by ellipses
is enclosed in brackets, zero or more options or operands can be
specified. The form:
utility_name [-g option_argument]...[operand...]
http://www.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html#tag_12_01
(& 12.1.9)
--
Nicolas Sebrecht
next prev parent reply other threads:[~2009-08-12 13:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 13:03 [PATCH] [TRIVIAL] Documentation: merge: one <remote> is required Paul Bolle
2009-08-11 14:42 ` [PATCH] " Nicolas Sebrecht
2009-08-11 14:58 ` Paul Bolle
2009-08-12 2:48 ` Junio C Hamano
2009-08-12 10:19 ` Jakub Narebski
2009-08-12 13:29 ` Nicolas Sebrecht [this message]
2009-08-12 10:56 ` Paul Bolle
2009-08-12 20:31 ` Junio C Hamano
2009-08-12 20:47 ` Paul Bolle
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=20090812132924.GA28345@vidovic \
--to=nicolas.s.dev@gmx.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=pebolle@tiscali.nl \
/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).