diff options
| author | Junio C Hamano <junkio@cox.net> | 2005-11-15 01:31:04 -0800 |
|---|---|---|
| committer | Junio C Hamano <junkio@cox.net> | 2005-11-15 01:31:04 -0800 |
| commit | cd0a781c386b197e63a30104bead39420eada7ca (patch) | |
| tree | 8ea8ba4b812ca2bc384ccc117da7fd4f4516f000 /Documentation/git-commit-tree.txt | |
| parent | Fix bunch of fd leaks in http-fetch (diff) | |
| download | git-cd0a781c386b197e63a30104bead39420eada7ca.tar.gz git-cd0a781c386b197e63a30104bead39420eada7ca.zip | |
Documentation: do not blindly run 'cat' .git/HEAD, or echo into it.
Many places in the documentation we still talked about reading
what commit is recorded in .git/HEAD or writing the new head
information into it, both assuming .git/HEAD is a symlink. That
is not necessarily so.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/git-commit-tree.txt')
| -rw-r--r-- | Documentation/git-commit-tree.txt | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/Documentation/git-commit-tree.txt b/Documentation/git-commit-tree.txt index 5cf6bd3e21..a794192d7b 100644 --- a/Documentation/git-commit-tree.txt +++ b/Documentation/git-commit-tree.txt @@ -26,8 +26,9 @@ to get there. Normally a commit would identify a new "HEAD" state, and while git doesn't care where you save the note about that state, in practice we -tend to just write the result to the file `.git/HEAD`, so that we can -always see what the last committed state was. +tend to just write the result to the file that is pointed at by +`.git/HEAD`, so that we can always see what the last committed +state was. OPTIONS ------- |