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

Re: Separate default push/pull?

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 12, 2010, 00:49 UTC
Message-ID
<7veikrl1m1.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20100212001417.GC21930@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
> I think what he would need is a "push.defaultRemote" config option,
> which universally overrides branch.*.remote for pushing.
Or "branch.*.pushremote".

But does it really make sense to get changes from one place and send changes to somewhere completely unrelated?

Previous: Jeff KingNext: Jeff King
Message 4 of 8 in “Separate default push/pull?”
  1. David AbrahamsFeb 11, 2010
  2. Chris PackhamFeb 11, 2010
  3. Jeff KingFeb 12, 2010
  4. Junio C HamanoFeb 12, 2010
  5. Jeff KingFeb 12, 2010
  6. Junio C HamanoFeb 12, 2010
  7. Jeff KingFeb 13, 2010
  8. David AbrahamsFeb 12, 2010

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.