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

Re: [BUG] inconsistent behavior with --set-upstream vs --set-upstream-to

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Apr 2, 2013, 19:08 UTC
Message-ID
<20130402190808.GH28148@google.com>
In-Reply-To
<A4C40BCB-85DD-4BCB-8BF0-79A75DE73211@gmail.com>
Garrett Cooper wrote:
> I push the branch to origin/ and then things tend to work, but since
> I obviously had been doing things wrong what's the correct order of
> operations for creating a branch and setting the upstream
> appropriately?
git push -u origin pjdfstest-onefs

Thanks for a useful example, Jonathan

Previous: Junio C Hamano
Message 15 of 15 in “[BUG] inconsistent behavior with --set-upstream vs --set-upstream-to”
  1. Garrett CooperApr 2, 2013
  2. Jeff KingApr 2, 2013
  3. Garrett CooperApr 2, 2013
  4. Jeff KingApr 2, 2013
  5. 0/5 branch --set-upstream-to error-message improvementsJeff King, Apr 2, 2013
  6. 1/5 t3200: test --set-upstream-to with bogus refsJeff King, Apr 2, 2013
  7. 2/5 branch: factor out "upstream is not a branch" error messagesJeff King, Apr 2, 2013
  8. Garrett CooperApr 2, 2013
  9. Garrett CooperApr 2, 2013
  10. 3/5 branch: improve error message for missing --set-upstream-to refJeff King, Apr 2, 2013
  11. 4/5 branch: mention start_name in set-upstream error messagesJeff King, Apr 2, 2013
  12. Garrett CooperApr 2, 2013
  13. 5/5 branch: give advice when tracking start-point is missingJeff King, Apr 2, 2013
  14. Junio C HamanoApr 2, 2013
  15. Jonathan NiederApr 2, 2013

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.