diff options
| author | Johan Herland <johan@herland.net> | 2011-02-16 00:54:24 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2011-02-16 18:21:52 (GMT) |
| commit | 53c403116a947c538132fc721f83196036f7a299 (patch) | |
| tree | e2c89a7ebdc7f121676c49475f78da442bc0dc1b /test-delta.c | |
| parent | 7ed863a85a6ce2c4ac4476848310b8f917ab41f9 (diff) | |
| download | git-53c403116a947c538132fc721f83196036f7a299.zip git-53c403116a947c538132fc721f83196036f7a299.tar.gz git-53c403116a947c538132fc721f83196036f7a299.tar.bz2 | |
push.default: Rename 'tracking' to 'upstream'
Users are sometimes confused with two different types of "tracking" behavior
in Git: "remote-tracking" branches (e.g. refs/remotes/*/*) versus the
merge/rebase relationship between a local branch and its @{upstream}
(controlled by branch.foo.remote and branch.foo.merge config settings).
When the push.default is set to 'tracking', it specifies that a branch should
be pushed to its @{upstream} branch. In other words, setting push.default to
'tracking' applies only to the latter of the above two types of "tracking"
behavior.
In order to make this more understandable to the user, we rename the
push.default == 'tracking' option to push.default == 'upstream'.
push.default == 'tracking' is left as a deprecated synonym for 'upstream'.
Signed-off-by: Johan Herland <johan@herland.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'test-delta.c')
0 files changed, 0 insertions, 0 deletions