{"thread":{"id":"9045","subject":"[PATCH] Minor addition to git-check-ref-format man page","startedAt":"2007-07-15T12:18:08Z","lastAt":"2007-07-15T12:18:08Z","messageCount":1,"participants":["Sean"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"47419","messageId":"20070715081808.17e0564e.seanlkml@sympatico.ca","threadId":"9045","inReplyTo":null,"subject":"[PATCH] Minor addition to git-check-ref-format man page","fromName":"Sean","fromEmail":"seanlkml@sympatico.ca","sentAt":"2007-07-15T12:18:08Z","receivedAt":"2007-07-15T12:18:08Z","isPatch":true,"sender":{"key":"seanlkml@sympatico.ca","avatar":"https://gravatar.com/avatar/f92923f54fc08c401fc59b71829d4b89e9b8087fbba45ff87c82e6a83aee02ae?d=mp&s=160"},"body":"\nMention that refname must include at least one slash to\nbe considered valid.\n\nSigned-off-by: Sean Estabrooks <seanlkml@sympatico.ca>\n---\n Documentation/git-check-ref-format.txt |   10 ++++++----\n 1 files changed, 6 insertions(+), 4 deletions(-)\n\ndiff --git a/Documentation/git-check-ref-format.txt b/Documentation/git-check-ref-format.txt\nindex 13a5f43..4f80053 100644\n--- a/Documentation/git-check-ref-format.txt\n+++ b/Documentation/git-check-ref-format.txt\n@@ -11,11 +11,13 @@ SYNOPSIS\n \n DESCRIPTION\n -----------\n-Checks if a given 'refname' is acceptable, and exits non-zero if\n-it is not.\n+Checks if a given 'refname' is acceptable and exits with zero if\n+it is all right.  To be considered acceptable, the refname must\n+contain at least one slash '/' character (eg. heads/master).\n \n A reference is used in git to specify branches and tags.  A\n-branch head is stored under `$GIT_DIR/refs/heads` directory, and\n+branch head is stored under `$GIT_DIR/refs/heads` directory, a\n+remote-branch head is stored under `$GIT_DIR/refs/remotes`, and\n a tag is stored under `$GIT_DIR/refs/tags` directory.  git\n imposes the following rules on how refs are named:\n \n@@ -32,7 +34,7 @@ imposes the following rules on how refs are named:\n \n . It cannot end with a slash `/`.\n \n-These rules makes it easy for shell script based tools to parse\n+These rules make it easy for shell script based tools to parse\n refnames, pathname expansion by the shell when a refname is used\n unquoted (by mistake), and also avoids ambiguities in certain\n refname expressions (see gitlink:git-rev-parse[1]).  Namely:\n-- \n1.5.2.2\n"}]}