| commit | bb35f35e67ed2fdfce1892cc9d55827b90fcb775 | |
| author | Jonathan Nieder <jrnieder@gmail.com> | |
| Fri, 9 Oct 2009 18:34:08 +0000 (9 13:34 -0500) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 9 Oct 2009 21:54:15 +0000 (9 14:54 -0700) | ||
| tree | 28bd4d73885be16c332ca88a2a0504f967b488ef | treesnapshot (tar.gz zip) |
| parent | 58d2c961b310d9366dd193f2d95d7eae56edecec | commitdiff |
Documentation: clarify branch creation
The documentation seems to assume that the starting point for a new
branch is the tip of an existing (ordinary) branch, but that is not
the most common case. More often, "git branch" is used to begin
a branch from a remote-tracking branch, a tag, or an interesting
commit (e.g. origin/pu^2). Clarify the language so it can apply
to these cases. Thanks to Sean Estabrooks for the wording.
Also add a pointer to the user's manual for the bewildered.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The documentation seems to assume that the starting point for a new
branch is the tip of an existing (ordinary) branch, but that is not
the most common case. More often, "git branch" is used to begin
a branch from a remote-tracking branch, a tag, or an interesting
commit (e.g. origin/pu^2). Clarify the language so it can apply
to these cases. Thanks to Sean Estabrooks for the wording.
Also add a pointer to the user's manual for the bewildered.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/git-branch.txt | diffblobblamehistory |