From: Pieter de Bie <pdebie@ai.rug.nl>
Date: Thu, 29 Jan 2009 11:40:42 GMT
Subject: Re: What's cooking in git.git (Jan 2009, #07; Wed, 28)
Message-ID: <351A6988-32EB-473F-B6E5-8FBB38D91F88@ai.rug.nl>
In-Reply-To: <20090129113735.GA6505@coredump.intra.peff.net>


On 29 jan 2009, at 11:37, Jeff King wrote:

>  git push origin master ;# note we have to explicitly mention the  
> branch
>
>  ... time passes ...
>
>  git pull
>
> produces the "you haven't asked me which branch to merge" message.
>
> Which does make some sense, given how tracking configuration is set  
> up.
> It's just that it's a little sad that cloning an empty repository and
> then later getting commits out of it (whether commits you put in or
> somebody else) does not behave the same as cloning a repository with
> commits.

This is true in all cases. If you create a new branch in any repository,
push that, and later do a 'git pull', you get that message. I agree it's
not the nicest way to handle things, but this is not an issue with the  
clone,
it's an issue of pushing new branches in general.