From: Junio C Hamano <gitster@pobox.com>
To: Abhijit Menon-Sen <ams@toroid.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Make it clear that push can take multiple refspecs
Date: Tue, 29 Jul 2008 16:20:00 -0700 [thread overview]
Message-ID: <7vwsj49t27.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080729231338.GA30717@toroid.org> (Abhijit Menon-Sen's message of "Wed, 30 Jul 2008 04:43:38 +0530")
Abhijit Menon-Sen <ams@toroid.org> writes:
> At 2008-07-29 15:06:57 -0700, gitster@pobox.com wrote:
>>
>> If you saw the question asked many times in the real world, that
>> would be a good indication that this patch falls into the "helpful"
>> category, not "noise". Will queue.
>
> Thanks.
>
> You may find the appended patch less noisy still. I certainly like being
> able to get rid of the "any number of..." sentence; and I also think the
> example is clearer, though I merged it into an existing one.
> ...
> -<refspec>::
> - The canonical format of a <refspec> parameter is
> +<refspec>...::
> + The canonical format of each <refspec> parameter is
> `+?<src>:<dst>`; that is, an optional plus `+`, followed
After re-reading this, prompted by your comment about "both synopsis
syntax and regex in the same sentence, I actually do not see a problem
with the original one. The synopsis talks about the ability for you to
specify zero or more of whatever is called <refspec>, and here we define
what _A_ refspec is.
Somehow I thought the issue was that we said "<refspec>...::" in the
heading of the description without saying zero-or-more, but that is not
the case here.
next prev parent reply other threads:[~2008-07-29 23:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 20:09 [PATCH] Make it clear that push can take multiple refspecs Abhijit Menon-Sen
2008-07-29 20:54 ` Junio C Hamano
2008-07-29 21:28 ` Abhijit Menon-Sen
2008-07-29 22:06 ` Junio C Hamano
2008-07-29 23:13 ` Abhijit Menon-Sen
2008-07-29 23:20 ` Junio C Hamano [this message]
2008-07-30 6:17 ` Abhijit Menon-Sen
2008-07-30 6:24 ` Junio C Hamano
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=7vwsj49t27.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=ams@toroid.org \
--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).