git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Include a git-push example for creating a remote branch

From
Miles Bader <miles@gnu.org>
Date
Sep 6, 2007, 05:57 UTC
Message-ID
<fc339e4a0709052257m4ddc5784obe64a8b75b79b19@mail.gmail.com>
In-Reply-To
<20070906050127.GS18160@spearce.org>
On 9/6/07, Shawn O. Pearce <spearce@spearce.org> wrote:
Show 9 quoted lines
> 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.
Previous: Shawn O. PearceNext: Junio C Hamano
Message 4 of 9 in “Include a git-push example for creating a remote branch”
  1. Include a git-push example for creating a remote branchShawn O. Pearce, Sep 6, 2007
  2. Miles BaderSep 6, 2007
  3. Shawn O. PearceSep 6, 2007
  4. Miles BaderSep 6, 2007
  5. Junio C HamanoSep 6, 2007
  6. Carl WorthSep 6, 2007
  7. Junio C HamanoSep 6, 2007
  8. Wincent ColaiutaSep 6, 2007
  9. Kristian HøgsbergSep 6, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.