git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 1/5] check-ref-format doc: de-emphasize the implementation detail of a ref

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 23, 2011, 16:52 UTC
Message-ID
<1308847958-3429-2-git-send-email-gitster@pobox.com>
In-Reply-To
<1308847958-3429-1-git-send-email-gitster@pobox.com>

It is an unimportant implementation detail that branches and tags are stored somewhere under $GIT_DIR/refs directory. What is more important is that branches live in refs/heads and tags live in refs/tags hierarchy in the ref namespace.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 Documentation/git-check-ref-format.txt |    9 ++++++---
 1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-check-ref-format.txt b/Documentation/git-check-ref-format.txt
index 205d83d..61471cf 100644
--- a/Documentation/git-check-ref-format.txt
+++ b/Documentation/git-check-ref-format.txt
@@ -18,9 +18,12 @@ Checks if a given 'refname' is acceptable, and exits with a non-zero
 status if it is not.
 
 A reference is used in git to specify branches and tags.  A
-branch head is stored under the `$GIT_DIR/refs/heads` directory, and
-a tag is stored under the `$GIT_DIR/refs/tags` directory (or, if refs
-are packed by `git gc`, as entries in the `$GIT_DIR/packed-refs` file).
+branch head is stored in the `refs/heads` hierarchy while
+a tag is stored in the `refs/tags` hierarchy of the ref namespace
+(which are found in `$GIT_DIR/refs/heads` and `$GIT_DIR/refs/tags`
+directories or, if refs are packed by `git gc`, as entries in
+the `$GIT_DIR/packed-refs` file).
+
 git imposes the following rules on how references are named:
 
 . They can include slash `/` for hierarchical (directory)
-- 
1.7.6.rc3
Previous: Junio C HamanoNext: Eric Sunshine
Message 8 of 16 in “git-remote.txt: fix wrong remote refspec”
  1. git-remote.txt: fix wrong remote refspecNamhyung Kim, Jun 23, 2011
  2. Junio C HamanoJun 23, 2011
  3. Namhyung KimJun 23, 2011
  4. git-remote.txt: fix wrong remote refspecNamhyung Kim, Jun 23, 2011
  5. Junio C HamanoJun 23, 2011
  6. Namhyung KimJun 23, 2011
  7. 0/5 Clarify "refs"Junio C Hamano, Jun 23, 2011
  8. 1/5 check-ref-format doc: de-emphasize the implementation detail of a refJunio C Hamano, Jun 23, 2011
  9. Eric SunshineJun 23, 2011
  10. 2/5 git.txt: de-emphasize the implementation detail of a refJunio C Hamano, Jun 23, 2011
  11. 3/5 glossary: update description of "tag"Junio C Hamano, Jun 23, 2011
  12. Eric SunshineJun 23, 2011
  13. 4/5 glossary: update description of head and refJunio C Hamano, Jun 23, 2011
  14. 5/5 glossary: clarify description of HEADJunio C Hamano, Jun 23, 2011
  15. Carlos Martín NietoJun 23, 2011
  16. Junio C HamanoJun 23, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.