Re: pull/push inconsistencies

From: Jeff King <peff@peff.net>
Date: May 16, 2007, 12:02 UTC
Message-ID: <20070516120237.GA11852@coredump.intra.peff.net>
In-Reply-To: <7vtzudhayr.fsf@assigned-by-dhcp.cox.net>

On Tue, May 15, 2007 at 05:24:28PM -0700, Junio C Hamano wrote:

Show 6 quoted lines

> > My second issue is that git-push does not update
> > remotes/<repo>/<headname> so if I do git-push && gitk --all it looks
> > as if I haven't pushed. Misleading again. :-/
> 
> The standard answer is not to push into a live repository
> without understanding what you are doing.

My impression here is that Martin is saying that pushing does not update the remote tracking branch in the local repository (as, e.g., cogito has always done). But I thought somebody (Ted?) recently submitted a patch to change that.

Show 6 quoted lines

> git-push without parameters and configuration pushes matching
> branches.  This has been true from day one.  Again, I think we
> should be able to make this safer so that "git-push" in cloned
> repository would do something more restricted (perhaps limiting
> to refs/heads?), but I do not think of a universally acceptable
> canned configuration.

I had done a patch in that direction (actually, it just avoided pushing refs/remotes/) and have been planning to follow up with restricting git-push to just refs/heads/. I'll try to work on that in the next day or so.

-Peff