Re: On fetch refspecs and wildcards

From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
	git@vger.kernel.org, Teemu Likonen <tlikonen@iki.fi>
Subject: Re: On fetch refspecs and wildcards
Date: Sun, 16 Mar 2008 15:33:05 -0700	[thread overview]
Message-ID: <7vve3mfgf2.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7v8x0igvdp.fsf_-_@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Sun, 16 Mar 2008 15:24:34 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> ...
> Fortunately or unfortunately, Documentation/pull-fetch-param.txt does not
> talk about wildcard refspecs (not even the syntax, let alone the
> semantics), so we can define whatever we want right now, and I think both
>
>     (1) allow duplicated destinations, including wildcard matches; and

Clarification.

"s/;/, but do honor requests to copy one thing to multiple destinations;/"
is what I meant here.

>     (2) refuse duplicated destinations for explicit ones, and more than
>         one wildcard patterns that match the same ref, but omit explicitly
>         specified ones from wildcard matches;
>
> are viable options.  I suspect the current code does not do either.  We
> should pick one semantics, make sure the implementation matches that, and
> document it.