Re: git push bug?

From: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Date: Oct 19, 2007, 14:47 UTC
Message-ID: <1192805255.1875.25.camel@gentoo-jocke.transmode.se>
In-Reply-To: <Pine.LNX.4.64.0710182259190.25221@racer.site>

On Thu, 2007-10-18 at 23:00 +0100, Johannes Schindelin wrote:

Show 24 quoted lines

> Hi,
> 
> On Thu, 18 Oct 2007, Joakim Tjernlund wrote:
> 
> > On Thu, 2007-10-18 at 17:21 +0100, Johannes Schindelin wrote:
> > 
> > > On Thu, 18 Oct 2007, Joakim Tjernlund wrote:
> > > 
> > > > Seems like it is a bit too easy to make mistakes here. Why can I 
> > > > delete a branch with :linus but not create one with linus:linus?
> > > 
> > > I wonder why you bother with the colon at all.  Just
> > > 
> > > 	git push <remote> linus
> > > 
> > > and be done with it.  The colon is only there to play interesting 
> > > games, not something as simple as "push this branch" or "push this 
> > > tag".
> > 
> > First, I didn't know that I could do that. Secondly, I was also looking 
> > do v2.6.23:linus refspecs
> 
> 
> First, then our documentation could be better.  How?

Well, it isn't clear to me how all this is supposed to work and what is bugs. Clearifying that would help.

For instances I did a push with v2.6.23:refs/heads/linus and now I got a branch with the SHA1 of v2.6.23 tag(0b8bc8b91cf6befea20fe78b90367ca7b61cfa0d) in it. Makes gitk display that branch as "linus^{}".

> 
> Second, why not "git checkout -b linus v2.6.23 && git push origin linus"?

An extra checkout that takes time but works. Doesn't make the above "weiredness" go away though.

 Jocke

Show 5 quoted lines

> 
> Ciao,
> Dscho
> 
>