Re: [PATCH v2 9/9] fetch: allow explicit --refmap to override configuration

2014-06-18 Thread Michael Haggerty
On 06/05/2014 08:36 PM, Junio C Hamano wrote: Marc Branchaud marcn...@xiplink.com writes: I don't have any objection to the option per se. But I do wonder if there's a need to add yet another knob to git just for completeness. Has anyone ever needed this? It is not a good yardstick, as

Re: [PATCH v2 9/9] fetch: allow explicit --refmap to override configuration

2014-06-05 Thread Marc Branchaud
On 14-06-04 06:28 PM, Junio C Hamano wrote: Marc Branchaud mbranch...@xiplink.com writes: Teach the command to pay attention to the --refmap=lhs:rhs command-line options that can be used to override the use of configured remote.*.fetch as the refmap. (Your 0/9 message merely said The new

Re: [PATCH v2 9/9] fetch: allow explicit --refmap to override configuration

2014-06-05 Thread Junio C Hamano
Marc Branchaud marcn...@xiplink.com writes: I don't have any objection to the option per se. But I do wonder if there's a need to add yet another knob to git just for completeness. Has anyone ever needed this? It is not a good yardstick, as everybody has survived without it since Git's

Re: [PATCH v2 9/9] fetch: allow explicit --refmap to override configuration

2014-06-04 Thread Marc Branchaud
On 14-06-03 06:16 PM, Junio C Hamano wrote: Since the introduction of opportunisitic updates of remote-tracking branches, started at around f2690487 (fetch: opportunistically update tracking refs, 2013-05-11) with a few updates in v1.8.4 era, the remote.*.fetch configuration always kicks in

Re: [PATCH v2 9/9] fetch: allow explicit --refmap to override configuration

2014-06-04 Thread Junio C Hamano
Marc Branchaud mbranch...@xiplink.com writes: Teach the command to pay attention to the --refmap=lhs:rhs command-line options that can be used to override the use of configured remote.*.fetch as the refmap. (Your 0/9 message merely said The new patches at the end clarifies how