summaryrefslogtreecommitdiff
path: root/t/t5515/fetch.br-config-explicit-octopus
diff options
context:
space:
mode:
authorLibravatar Jonathan Nieder <jrnieder@gmail.com>2009-10-09 13:34:08 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2009-10-09 14:54:15 -0700
commitbb35f35e67ed2fdfce1892cc9d55827b90fcb775 (patch)
tree28bd4d73885be16c332ca88a2a0504f967b488ef /t/t5515/fetch.br-config-explicit-octopus
parentDocumentation: branch: update --merged description (diff)
downloadtgif-bb35f35e67ed2fdfce1892cc9d55827b90fcb775.tar.xz
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>
Diffstat (limited to 't/t5515/fetch.br-config-explicit-octopus')
0 files changed, 0 insertions, 0 deletions