This new configuration variable overrides `remote.pushdefault` and
`branch.name.remote` for pushes. When you pull from one
place (e.g. your upstream) and push to another place (e.g. your own
publishing repository), you would want to set `remote.pushdefault` to
specify the remote to push to for
This new configuration variable overrides `remote.pushdefault` and
`branch.name.remote` for pushes. When you pull from one
place (e.g. your upstream) and push to another place (e.g. your own
publishing repository), you would want to set `remote.pushdefault` to
specify the remote to push to for
Ramkumar Ramachandra artag...@gmail.com writes:
This new configuration variable overrides `remote.pushdefault` and
`branch.name.remote` for pushes. In a typical triangular-workflow
setup, you would want to set `remote.pushdefault` to specify the
remote to push to for all branches, and use
On Wed, Mar 20, 2013 at 8:45 PM, Ramkumar Ramachandra
artag...@gmail.com wrote:
This new configuration variable overrides `remote.pushdefault` and
`branch.name.remote` for pushes. In a typical triangular-workflow
setup, you would want to set `remote.pushdefault` to specify the
remote to push
Tay Ray Chuan wrote:
On Wed, Mar 20, 2013 at 8:45 PM, Ramkumar Ramachandra
artag...@gmail.com wrote:
This new configuration variable overrides `remote.pushdefault` and
`branch.name.remote` for pushes. In a typical triangular-workflow
setup, you would want to set `remote.pushdefault` to
5 matches
Mail list logo