On Mon, Nov 8, 2010 at 8:48 AM, Jakub Narebski <jnareb@xxxxxxxxx> wrote: > On Mon, 8 Nov 2010, Martin von Zweigbergk wrote: >> Sorry, maybe I misunderstood what the confusion was about. What I was >> referring to was the confusion caused by 'git fetch origin master' not >> updating 'refs/remotes/origin/master'. > > Should it really do it? What if it does not exist? What if <remote> > is specified via URL? I would probably not expect it to be updated (even if the URL matches a configured remove). If the reference does not yet exist, I think I would expect it to be created. > If I understand correctly current behavior of 'git fetch <remote> <branch>' > wrt. FETCH_HEAD was meant for one-off 'git pull <remote> <branch>', or > rather 'git pull <URL> <branch>'. Also see http://thread.gmane.org/gmane.comp.version-control.git/127163/. Junio, Jeff and Avery can argue much better for and against this than I can. I read it at some point, but I don't quite remember now if they did discuss the historical reasons for the current behavior in that thread. /Martin -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html