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

Re: error with $ git push origin HEAD:newbranch

From
Junio C Hamano <gitster@pobox.com>
Date
May 6, 2011, 04:56 UTC
Message-ID
<7v39ks4ebd.fsf@alter.siamese.dyndns.org>
In-Reply-To
<loom.20110506T034552-210@post.gmane.org>
chris <jugg@hotmail.com> writes:
> All of that to say, it isn't exactly clear what one should expect.

The take-home lesson is that if you want to be explicit and exactly clear, you can and should spell things out in full, and you can sleep well at night if you did so.

	# Let's call retroactively v1.5 without the last three topic
        # merges the v1.4.9 release...
	$ git push origin v1.5~3:refs/tags/v1.4.9
Previous: chrisNext: chris
Message 6 of 11 in “error with $ git push origin HEAD:newbranch”
  1. chrisMay 5, 2011
  2. Jeff KingMay 5, 2011
  3. chrisMay 5, 2011
  4. Jeff KingMay 5, 2011
  5. chrisMay 6, 2011
  6. Junio C HamanoMay 6, 2011
  7. chrisMay 6, 2011
  8. Jeff KingMay 6, 2011
  9. chrisMay 10, 2011
  10. Jeff KingMay 10, 2011
  11. chrisMay 11, 2011

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.