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

docu. concerning push and remotes

From
MMichaelTiloDressel@t-online.de <michaeltilodressel@t-online.de>
Date
Jan 25, 2008, 15:09 UTC
Message-ID
<1JIQBK-1ueKMy0@fwd35.aul.t-online.de>
Hi,

the man page of git-config explains that branch.<name>.remote has an influence on the default behavior of fetch. It looks like it also has an influence on the default of push. This is what I was looking for. But I could not find that influence on push documented.

I found that I had to setup branch.<name>.remote (and branch.<name>.merge) entries for my branches in order to have only the current branch pushed when I use git push without arguments. That's what I want. If I don't have these settings all branches get pushed. In addition a separate remote has to exist for every branch.

Somehow I feel this should be mentioned in the man page of git-config or
git-push.

Cheers, Michael

Message 1 of 1 in “docu. concerning push and remotes”
  1. MichaelTiloDressel@t-online.deJan 25, 2008

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.