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

Re: [PATCH 4/4] remote.c: introduce branch.<name>.pushremote

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Mar 18, 2013, 22:23 UTC
Message-ID
<CAPig+cQ5-07+oRYCym+9wA-C020oZ3V9_ZhE8o_RU-1OGqhpmg@mail.gmail.com>
In-Reply-To
<1363612575-7340-5-git-send-email-artagnon@gmail.com>

On Mon, Mar 18, 2013 at 9:16 AM, Ramkumar Ramachandra <artagnon@gmail.com> wrote:

Show 5 quoted lines
> -       If no remote is configured, or if you are not on any branch,
> -       it defaults to `origin` for fetching and `remote.pushdefault`
> -       for pushing.
> +       The remote to push to, for the current branch, may be further
> +       overriden by `branch.<name>.pushremote`.  If no remote is
s/overriden/overridden/
Show 7 quoted lines
> +       configured, or if you are not on any branch, it defaults to
> +       `origin` for fetching and `remote.pushdefault` for pushing.
> +
>  remote.pushdefault::
>         The remote to push to by default.  Overrides
> -       `branch.<name>.remote` for all branches.
> +       `branch.<name>.remote` for all branches, and is overriden by
Ditto: s/overriden/overridden/
> +       `branch.<name>.pushremote` for specific branches.
Previous: Ramkumar RamachandraNext: Jeff King
Message 12 of 16 in “Support triangular workflows”
  1. 0/4 Support triangular workflowsRamkumar Ramachandra, Mar 18, 2013
  2. 1/4 remote.c: simply a bit of code using git_config_string()Ramkumar Ramachandra, Mar 18, 2013
  3. Eric SunshineMar 18, 2013
  4. 2/4 remote.c: introduce a way to have different remotes for fetch/ pushRamkumar Ramachandra, Mar 18, 2013
  5. Jeff KingMar 18, 2013
  6. Ramkumar RamachandraMar 18, 2013
  7. Jeff KingMar 18, 2013
  8. Eric SunshineMar 18, 2013
  9. 3/4 remote.c: introduce remote.pushdefaultRamkumar Ramachandra, Mar 18, 2013
  10. Eric SunshineMar 18, 2013
  11. 4/4 remote.c: introduce branch.<name>.pushremoteRamkumar Ramachandra, Mar 18, 2013
  12. Eric SunshineMar 18, 2013
  13. Jeff KingMar 18, 2013
  14. Ramkumar RamachandraMar 18, 2013
  15. Jeff KingMar 18, 2013
  16. Marc BranchaudMar 18, 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.