| commit | 0aceb220972413e73157cb46a8a52e0f6034d54c | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Thu, 23 Jun 2011 15:33:05 +0000 (23 08:33 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 23 Jun 2011 16:15:28 +0000 (23 09:15 -0700) | ||
| tree | 74e48e28ac7038b85a174797c7cd6cd8008f470a | treesnapshot (tar.gz zip) |
| parent | eb637e138289dc5b96bea5b192cbaff93623d1dc | commitdiff |
git-remote.txt: avoid sounding as if loose refs are the only ones in the world
It was correct to say "The file $GIT_DIR/refs/heads/master stores the
commit object name at the tip of the master branch" in the older days,
but not anymore, as refs can be packed into $GIT_DIR/packed-refs file.
Update the document to talk in terms of a more abstract concept "ref" and
"symbolic ref" where we are not describing the underlying implementation
detail.
This on purpose leaves two instances of $GIT_DIR/ in the git-remote
documentation; they do talk about $GIT_DIR/remotes/ and $GIT_DIR/branches/
file hierarchy that used to be the place to store configuration around
remotes before the configuration mechanism took them over.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
It was correct to say "The file $GIT_DIR/refs/heads/master stores the
commit object name at the tip of the master branch" in the older days,
but not anymore, as refs can be packed into $GIT_DIR/packed-refs file.
Update the document to talk in terms of a more abstract concept "ref" and
"symbolic ref" where we are not describing the underlying implementation
detail.
This on purpose leaves two instances of $GIT_DIR/ in the git-remote
documentation; they do talk about $GIT_DIR/remotes/ and $GIT_DIR/branches/
file hierarchy that used to be the place to store configuration around
remotes before the configuration mechanism took them over.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/git-remote.txt | diffblobblamehistory |