From 2069ab0a1092b2d6ee292de0a3a6d714867cd01f Mon Sep 17 00:00:00 2001 From: Alex Blewitt Date: Mon, 17 Jan 2022 10:07:08 +0000 Subject: [PATCH] doc: update ref/ to refs/ The documentation referred to `ref/head` and `ref/tags`. Correct this to use the conventional `refs/heads` and `refs/tags` instead. Signed-off-by: Alex Blewitt --- Documentation/git.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/git.txt b/Documentation/git.txt index 13f83a2a3a1220..f03cedec73664b 100644 --- a/Documentation/git.txt +++ b/Documentation/git.txt @@ -986,9 +986,9 @@ efficiency may later be compressed together into "pack files". Named pointers called refs mark interesting points in history. A ref may contain the SHA-1 name of an object or the name of another ref. Refs -with names beginning `ref/head/` contain the SHA-1 name of the most +with names beginning `refs/heads/` contain the SHA-1 name of the most recent commit (or "head") of a branch under development. SHA-1 names of -tags of interest are stored under `ref/tags/`. A special ref named +tags of interest are stored under `refs/tags/`. A special ref named `HEAD` contains the name of the currently checked-out branch. The index file is initialized with a list of all paths and, for each