Re: What's cooking in git.git (Jan 2009, #07; Wed, 28)

From: Jeff King <peff@peff.net>
Date: Jan 29, 2009, 11:50 UTC
Message-ID: <20090129115026.GB10792@coredump.intra.peff.net>
In-Reply-To: <bd6139dc0901290345u4962f747gbe93c945ab35c9cb@mail.gmail.com>

On Thu, Jan 29, 2009 at 12:45:23PM +0100, Sverre Rabbelier wrote:

Show 9 quoted lines

> On Thu, Jan 29, 2009 at 12:40, Pieter de Bie <pdebie@ai.rug.nl> wrote:
> > 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.
> 
> Mhhh, so maybe we want a way to set up tracking branches when pushing,
> yes? From what I've seen a patch to do that shouldn't be too hard, so
> if there's interest in that I could look into that.

I think that would be reasonable. It wouldn't help the case of "somebody else pushed some content that you want to pull", but like you said, I think the primary workflow is that you immediately push after cloning the empty repo.

-Peff