aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-01-31 12:50:38 -0800
committerJunio C Hamano <gitster@pobox.com>2013-01-31 17:00:56 -0800
commitfa23348e95a3a98ca42a4b74e8f17fb52b95ded8 (patch)
treec64e8bb035d96f2170555de53c3870aea640e49d
parent7e2010537e96d0a1144520222f20ba1dc3d61441 (diff)
downloadgit-fa23348e95a3a98ca42a4b74e8f17fb52b95ded8.tar.gz
git-fa23348e95a3a98ca42a4b74e8f17fb52b95ded8.tar.xz
doc: mention tracking for pull.default
When looking at a configuration file edited long time ago, a user may find 'pull.default = tracking' and wonder what it means, but earlier we stopped mentioning this value, even though the code still support it and more importantly, we have no intention to force old timers to update their configuration files. Instead of not mentioning it, add it to the description in a way that makes it clear that users have no reason to add new uses of it preferring over 'upstream', by not listing it as a separate item on the same footing as other values but as a deprecated synonym of the 'upstream' in its description. Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/config.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/config.txt b/Documentation/config.txt
index 122e3c499..10e28560e 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -1749,7 +1749,8 @@ push.default::
+
This is currently the default, but Git 2.0 will change the default
to `simple`.
-* `upstream` - push the current branch to its upstream branch.
+* `upstream` - push the current branch to its upstream branch
+ (`tracking` is a deprecated synonym for this).
With this, `git push` will update the same remote ref as the one which
is merged by `git pull`, making `push` and `pull` symmetrical.
See "branch.<name>.merge" for how to configure the upstream branch.