From: "Miles Bader" <miles@gnu.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Include a git-push example for creating a remote branch
Date: Thu, 6 Sep 2007 14:57:26 +0900 [thread overview]
Message-ID: <fc339e4a0709052257m4ddc5784obe64a8b75b79b19@mail.gmail.com> (raw)
In-Reply-To: <20070906050127.GS18160@spearce.org>
On 9/6/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> Miles Bader <miles.bader@necel.com> wrote:
> > > Many users get confused when `git push origin master:foo` works
> > > when foo already exists on the remote repository but are confused
> > > when foo doesn't exist as a branch and this form does not create
> > > the branch foo.
> >
> > Hmm, what _does_ it do in that case...?
>
> error: dst refspec experimental does not match any existing ref on the remote and does not start with refs/.
Hmm, I'm assuming people don't want to default to just creating a new
remote ref ('cause it might be too easy to muck up a remote archive
that way), but it seems like it would be nice to have a "prettier" way
to create a remote ref than explicitly giving the whole ref path on
the remote side.
Maybe I"m weird, but I tend to think of the refs/... syntax as being
for "only if you're doing something funny" cases.
I'm thinking of something like:
... create new local branch "zoink" ...
git push --create origin zoink
-Miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2007-09-06 5:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 4:44 [PATCH] Include a git-push example for creating a remote branch Shawn O. Pearce
2007-09-06 4:54 ` Miles Bader
2007-09-06 5:01 ` Shawn O. Pearce
2007-09-06 5:57 ` Miles Bader [this message]
2007-09-06 6:30 ` Junio C Hamano
2007-09-06 15:48 ` Carl Worth
2007-09-06 17:42 ` Junio C Hamano
2007-09-06 10:50 ` Wincent Colaiuta
2007-09-06 14:57 ` Kristian Høgsberg
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fc339e4a0709052257m4ddc5784obe64a8b75b79b19@mail.gmail.com \
--to=miles@gnu.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).