From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Steffen Prohaska <prohaska@zib.de>
Cc: Joakim Tjernlund <joakim.tjernlund@transmode.se>,
git <git@vger.kernel.org>
Subject: Re: git push bug?
Date: Thu, 18 Oct 2007 22:58:22 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710182258000.25221@racer.site> (raw)
In-Reply-To: <9EEDF284-22BE-44BF-A9B8-116407784BEB@zib.de>
Hi,
On Thu, 18 Oct 2007, Steffen Prohaska wrote:
> On Oct 18, 2007, at 6:21 PM, 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".
>
> But you need a full refspec starting with 'refs/heads/' if you want to
> create a new branch on the remote side.
No. Not if the name is the same on the local side.
Ciao,
Dscho
next prev parent reply other threads:[~2007-10-18 21:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 14:50 git push bug? Joakim Tjernlund
2007-10-18 15:14 ` Steffen Prohaska
2007-10-18 16:01 ` Joakim Tjernlund
2007-10-18 16:10 ` Joakim Tjernlund
2007-10-19 0:49 ` Shawn O. Pearce
2007-10-18 16:13 ` Steffen Prohaska
2007-10-18 16:21 ` Johannes Schindelin
2007-10-18 16:31 ` Joakim Tjernlund
2007-10-18 22:00 ` Johannes Schindelin
2007-10-19 14:47 ` Joakim Tjernlund
2007-10-19 17:24 ` Johannes Schindelin
2007-10-19 18:50 ` Joakim Tjernlund
2007-10-19 22:46 ` Johannes Schindelin
2007-10-20 12:05 ` Jan Hudec
2007-10-18 16:55 ` Steffen Prohaska
2007-10-18 21:58 ` Johannes Schindelin [this message]
2007-10-20 8:29 ` Steffen Prohaska
2007-10-20 8:38 ` Steffen Prohaska
2007-10-20 11:52 ` Joakim Tjernlund
2007-10-19 0:24 ` Shawn O. Pearce
2007-10-20 17:38 ` Joakim Tjernlund
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0710182258000.25221@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=joakim.tjernlund@transmode.se \
--cc=prohaska@zib.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).