Thread (4 messages) flat view 4 messages, 3 authors, 2016-06-15

Re: [RFC/PATCH] clone: make 'git clone -c remote.origin.fetch=<refspec>' work

From: Junio C Hamano <hidden>
Date: 2016-06-15 23:08:39

Possibly related (same subject, not in this thread)

SZEDER Gábor [off-list ref] writes:
Check whether there are any relevant configured fetch refspecs and
take those into account during the initial fetch, unless running 'git
clone --single-branch'.

Signed-off-by: SZEDER Gábor <redacted>
---
Even though I think the original description did not mean to include
the fetch refspecs when it talked about configuration taking effect, 
I think what this change wants to do probably makes sense.
I'm unsure what to do with the '-c <fetch-refspec> --single-branch'
combination: it doesn't really make sense to me and can't imagaine a
use case where it would be useful...  but perhaps I just lack
imagination on this Sunday night.  Hence the RFC.
My knee-jerk reaction is to change the last paragraph of your log
message to read more like

	Always read the fetch refspecs from the newly created config
	file, and use that for the initial fetching.

and do so even when running with "--single-branch".
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help