Re: [PATCH] fetch: don't try to update unfetched tracking refs

On Mon, May 27, 2013 at 05:01:29PM +0100, John Keeping wrote: > > I'm not sure I understand what the last sentence means. I tried to add a > > test like: > [...] > > but it does not fail with the existing code. Can you give an example > > that fails? > > I have this in my .git/config for git.git:

Re: [PATCH] fetch: don't try to update unfetched tracking refs

On Mon, May 27, 2013 at 11:42:52AM -0400, Jeff King wrote: > On Mon, May 27, 2013 at 12:40:25PM +0100, John Keeping wrote: > > > Since commit f269048 (fetch: opportunistically update tracking refs, > > 2013-05-11) we update tracking refs opportunistically when fetching > > remote branches. Howeve

Re: [PATCH] fetch: don't try to update unfetched tracking refs

On Mon, May 27, 2013 at 12:40:25PM +0100, John Keeping wrote: > Since commit f269048 (fetch: opportunistically update tracking refs, > 2013-05-11) we update tracking refs opportunistically when fetching > remote branches. However, if a refspec is given on the command line > that does not include

[PATCH] fetch: don't try to update unfetched tracking refs

Since commit f269048 (fetch: opportunistically update tracking refs, 2013-05-11) we update tracking refs opportunistically when fetching remote branches. However, if a refspec is given on the command line that does not include a configured (non-pattern) refspec a fatal error occurs. Fix this by s