{"thread":{"id":"11733","subject":"docu. concerning push and remotes","startedAt":"2008-01-25T15:09:26Z","lastAt":"2008-01-25T15:09:26Z","messageCount":1,"participants":["MichaelTiloDressel@t-online.de"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"66571","messageId":"1JIQBK-1ueKMy0@fwd35.aul.t-online.de","threadId":"11733","inReplyTo":null,"subject":"docu. concerning push and remotes","fromName":"MichaelTiloDressel@t-online.de","fromEmail":"michaeltilodressel@t-online.de","sentAt":"2008-01-25T15:09:26Z","receivedAt":"2008-01-25T15:09:26Z","isPatch":false,"sender":{"key":"michaeltilodressel@t-online.de","avatar":null},"body":"Hi,\n\nthe man page of git-config explains that branch.<name>.remote has an\ninfluence on\nthe default behavior of fetch. It looks like it also has an influence on\nthe default of push. \nThis is what I was looking for. But I could not find that influence on\npush documented.  \n\nI found that I had to setup branch.<name>.remote (and\nbranch.<name>.merge)\nentries for my branches in order to have only the current branch pushed\nwhen I use git push without arguments.\nThat's what I want. If I don't have these settings all branches get\npushed.\nIn addition a separate remote has to exist for every branch.\n\nSomehow I feel this should be mentioned in the man page of git-config or\n\ngit-push.\n\nCheers,\nMichael\n"}]}