From 89ce391b8edae97bbfd0fdb33b4c252b6fd0dc53 Mon Sep 17 00:00:00 2001 From: Max Horn Date: Fri, 6 Jul 2012 02:01:29 +0200 Subject: [PATCH] Make documentation more consistent. Formerly, the documentation for would occasionally say instead of . Now it uniformly uses . Signed-off-by: Max Horn Signed-off-by: Junio C Hamano --- Documentation/revisions.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt index 172566183..f4f6f281a 100644 --- a/Documentation/revisions.txt +++ b/Documentation/revisions.txt @@ -24,22 +24,22 @@ blobs contained in a commit. object referenced by 'refs/heads/master'. If you happen to have both 'heads/master' and 'tags/master', you can explicitly say 'heads/master' to tell git which one you mean. - When ambiguous, a '' is disambiguated by taking the + When ambiguous, a '' is disambiguated by taking the first match in the following rules: - . If '$GIT_DIR/' exists, that is what you mean (this is usually + . If '$GIT_DIR/' exists, that is what you mean (this is usually useful only for 'HEAD', 'FETCH_HEAD', 'ORIG_HEAD', 'MERGE_HEAD' and 'CHERRY_PICK_HEAD'); - . otherwise, 'refs/' if it exists; + . otherwise, 'refs/' if it exists; . otherwise, 'refs/tags/' if it exists; - . otherwise, 'refs/heads/' if it exists; + . otherwise, 'refs/heads/' if it exists; - . otherwise, 'refs/remotes/' if it exists; + . otherwise, 'refs/remotes/' if it exists; - . otherwise, 'refs/remotes//HEAD' if it exists. + . otherwise, 'refs/remotes//HEAD' if it exists. + 'HEAD' names the commit on which you based the changes in the working tree. 'FETCH_HEAD' records the branch which you fetched from a remote repository -- 2.26.2