summaryrefslogtreecommitdiff
path: root/t/t4134-apply-submodule.sh
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2013-04-05 08:19:41 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2013-04-05 10:42:58 -0700
commit1d77d249f9b0605ed21ca751c5dfb8550efcdfa3 (patch)
tree35aa5ba5c5e22985a00f7d1f77d12170bcc5a51d /t/t4134-apply-submodule.sh
parentDocumentation/git-commit: reword the --amend explanation (diff)
downloadtgif-1d77d249f9b0605ed21ca751c5dfb8550efcdfa3.tar.xz
glossary: extend "detached HEAD" description
When we introduced the concept of "detached HEAD", we made sure that commands that operate on the history of the current branch "just work" in that state. They update the HEAD to point at the new history without affecting any branch when the HEAD is detached, just like they update the tip of the "current branch" to point at the new history when HEAD points at a specific branch. As this is done as the natural extension for these commands, we did not, we still do not, and we do not want to repeat "A detached HEAD is updated without affecting any branch" when describing what each and every one of these commands that operates "on the current branch" does. Add a blanket description to the glossary to cover them instead. The general principle is that operations to update the branch work on and affect the HEAD, while operations to update the information about a branch do not. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4134-apply-submodule.sh')
0 files changed, 0 insertions, 0 deletions