summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 70e9664)
raw | patch | inline | side by side (parent: 70e9664)
author | Jeff King <peff@peff.net> | |
Mon, 13 Apr 2009 11:11:56 +0000 (07:11 -0400) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Mon, 13 Apr 2009 16:02:18 +0000 (09:02 -0700) |
The term "tracking" often creates confusion between remote
tracking branches and local branches which track a remote
branch. The term "upstream" captures more clearly the idea
of "branch A is based on branch B in some way", so it makes
sense to mention it.
At the same time, upstream branches are used for more
than just git-pull these days; let's mention that here.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
tracking branches and local branches which track a remote
branch. The term "upstream" captures more clearly the idea
of "branch A is based on branch B in some way", so it makes
sense to mention it.
At the same time, upstream branches are used for more
than just git-pull these days; let's mention that here.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-branch.txt | patch | blob | history | |
Documentation/git-checkout.txt | patch | blob | history |
index 19f1b0d9f9663c80fe708b89a1a3293cac314ac6..cbd427587188d81726445183f772f02982736e6a 100644 (file)
Display the full sha1s in the output listing rather than abbreviating them.
--track::
- When creating a new branch, set up the configuration so that 'git-pull'
- will automatically retrieve data from the start point, which must be
- a branch. Use this if you always pull from the same upstream branch
- into the new branch, and if you do not want to use "git pull
- <repository> <refspec>" explicitly. This behavior is the default
- when the start point is a remote branch. Set the
- branch.autosetupmerge configuration variable to `false` if you want
- 'git-checkout' and 'git-branch' to always behave as if '--no-track' were
- given. Set it to `always` if you want this behavior when the
- start-point is either a local or remote branch.
+ When creating a new branch, set up configuration to mark the
+ start-point branch as "upstream" from the new branch. This
+ configuration will tell git to show the relationship between the
+ two branches in `git status` and `git branch -v`. Furthermore,
+ it directs `git pull` without arguments to pull from the
+ upstream when the new branch is checked out.
++
+This behavior is the default when the start point is a remote branch.
+Set the branch.autosetupmerge configuration variable to `false` if you
+want `git checkout` and `git branch` to always behave as if '--no-track'
+were given. Set it to `always` if you want this behavior when the
+start-point is either a local or remote branch.
--no-track::
- Do not set up tracking configuration, even if the
+ Do not set up "upstream" configuration, even if the
branch.autosetupmerge configuration variable is true.
--contains <commit>::
index 4992fc61eba5213068d6c3a0307d5e2d13c968a9..16d3c872a056eed29806d96e4de2544963df72bd 100644 (file)
explicitly give a name with '-b' in such a case.
--no-track::
- Do not set up tracking configuration, even if the
+ Do not set up "upstream" configuration, even if the
branch.autosetupmerge configuration variable is true.
-l::