On Thu, May 16, 2013 at 5:32 AM, Ramkumar Ramachandra <artagnon@xxxxxxxxx> wrote: > Felipe Contreras wrote: >> Answer: because 'git fetch .' doesn't make any sense. So if >> 'branch.HEAD.remote' is '.' it doesn't make sense to do 'git fetch .'. > > I agree that 'git fetch .' is currently not useful (and I am not > against changing its behavior), but my question pertains to why you > are replacing it with the hard-coded "origin". 'origin' is already hard-coded. % git clone git://git.kernel.org/pub/scm/git/git.git What would be the name of the remote? 'origin'. % git checkout --no-track -b test % git fetch What is the remote that is used? 'origin'. > What happens when I > git branch -t -b devel hot-branch where branch.hot-branch.remote = ram > and not origin? The same thing that happens when you git branch --no-track -b devel hot-branch. -- Felipe Contreras -- 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