On Tue, Jul 7, 2015 at 9:24 PM, Junio C Hamano wrote:
> Jacob Keller writes:
>
>> +remote..arbitrarypattern::
>> + When set to true, fetching from this remote will allow arbitrary
>> complex
>> + patterns for the fetch refspecs. For example,
>> + refs/tags/prefix-*:refs/tags/prefix-*
Jacob Keller writes:
> +remote..arbitrarypattern::
> + When set to true, fetching from this remote will allow arbitrary complex
> + patterns for the fetch refspecs. For example,
> + refs/tags/prefix-*:refs/tags/prefix-* will work as expected. Care
> should be
> + taken as you cou
This patch updates the refs.c check_refname_component logic in order to
allow for the possibility of using arbitrary patterns in fetch refspecs.
Specifically, patterns similar to `refs/tags/prefix-*:refs/tags/prefix-*`.
In order to ensure that standard users do not accidentally setup refspecs
whic
3 matches
Mail list logo