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

Re: branch.<name>.pushremote not working with push.default simple or upstream

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Jun 7, 2013, 17:33 UTC
Message-ID
<CALkWK0=FnZUBXMJjSKgrbunDn3TtME-1tw++B5FimJx5=K_1qQ@mail.gmail.com>
In-Reply-To
<20130607170752.GI28668@sociomantic.com>
Leandro Lucarella wrote:
> I might try to just switch to current, I feel more comfortable with
> simple because I feel is safer to explicitly set the upstream branch,
> but is true that most of the time is not necessary.

Be more experimental! Use the lesser-known features, and tell us about breakages: that's how you can help git improve :)

Previous: Leandro LucarellaNext: Ramkumar Ramachandra
Message 7 of 9 in “branch.<name>.pushremote not working with push.default simple or upstream”
  1. Leandro LucarellaJun 7, 2013
  2. Ramkumar RamachandraJun 7, 2013
  3. Junio C HamanoJun 7, 2013
  4. Leandro LucarellaJun 7, 2013
  5. Ramkumar RamachandraJun 7, 2013
  6. Leandro LucarellaJun 7, 2013
  7. Ramkumar RamachandraJun 7, 2013
  8. Ramkumar RamachandraJun 7, 2013
  9. Junio C HamanoJun 7, 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.