{"thread":{"id":"40934","subject":"[PATCH] git-check-ref-format.txt: typo, s/avoids/avoid/","startedAt":"2015-12-04T18:09:32Z","lastAt":"2015-12-04T18:09:32Z","messageCount":1,"participants":["Nguyễn Thái Ngọc Duy"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"274013","messageId":"1449252572-5771-1-git-send-email-pclouds@gmail.com","threadId":"40934","inReplyTo":null,"subject":"[PATCH] git-check-ref-format.txt: typo, s/avoids/avoid/","fromName":"Nguyễn Thái Ngọc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2015-12-04T18:09:32Z","receivedAt":"2015-12-04T18:09:32Z","isPatch":true,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>\n---\n Documentation/git-check-ref-format.txt | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/Documentation/git-check-ref-format.txt b/Documentation/git-check-ref-format.txt\nindex 9044dfa..91a3622 100644\n--- a/Documentation/git-check-ref-format.txt\n+++ b/Documentation/git-check-ref-format.txt\n@@ -60,7 +60,7 @@ Git imposes the following rules on how references are named:\n \n These rules make it easy for shell script based tools to parse\n reference names, pathname expansion by the shell when a reference name is used\n-unquoted (by mistake), and also avoids ambiguities in certain\n+unquoted (by mistake), and also avoid ambiguities in certain\n reference name expressions (see linkgit:gitrevisions[7]):\n \n . A double-dot `..` is often used as in `ref1..ref2`, and in some\n-- \n2.2.0.513.g477eb31\n"}]}