Re: The fetch command should "always" honor remote..fetch

2014-04-09 Thread Lewis Diamond
plugin. -Lewis On Tue, Apr 8, 2014 at 9:45 PM, Junio C Hamano wrote: > Lewis Diamond writes: > >>>> 'git fetch foo master' would result in (FETCH_HEAD omitted): >>>> [new ref] refs/heads/master -> foo/master //OK, but missing another >>>> re

Re: The fetch command should "always" honor remote..fetch

2014-04-07 Thread Lewis Diamond
On Mon, Apr 7, 2014 at 2:23 PM, Junio C Hamano wrote: > Lewis Diamond writes: > >> 'git fetch foo develop' would result in: >> fatal: Couldn't find remote ref test2 //Not OK, (case 1) > > I have no idea where the "test2" comes from, as it does no

The fetch command should "always" honor remote..fetch

2014-04-05 Thread Lewis Diamond
). If multiple matches exist and have conflicting refspec->dst, error out (or should we honour the first matching refspec?). Note that for the 2nd rule, if remote->fetch_refspec doesn't include refs/heads/*, it means I went through the trouble of removing it from the configuration. Theref