{"thread":{"id":"50666","subject":"[PATCH] attr.c: \".gitattribute\" -> \".gitattributes\" (comments)","startedAt":"2019-03-06T09:14:55Z","lastAt":"2019-03-06T09:14:55Z","messageCount":1,"participants":["Robert P. J. Day"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"370794","messageId":"alpine.LFD.2.21.1903060413140.16835@localhost.localdomain","threadId":"50666","inReplyTo":null,"subject":"[PATCH] attr.c: \".gitattribute\" -> \".gitattributes\" (comments)","fromName":"Robert P. J. Day","fromEmail":"rpjday@crashcourse.ca","sentAt":"2019-03-06T09:14:44Z","receivedAt":"2019-03-06T09:14:55Z","isPatch":true,"sender":{"key":"rpjday@crashcourse.ca","avatar":"https://avatars.githubusercontent.com/u/226084077?v=4"},"body":"\nCorrect misspelled \".gitattribute\" in comments only, so no functional\nchange.\n\nSigned-off-by: Robert P. J. Day <rpjday@crashcourse.ca>\n\n---\n\ndiff --git a/attr.c b/attr.c\nindex fdd110bec5..93dc16b59c 100644\n--- a/attr.c\n+++ b/attr.c\n@@ -431,14 +431,14 @@ static struct match_attr *parse_attr_line(const char *line, const char *src,\n  * Like info/exclude and .gitignore, the attribute information can\n  * come from many places.\n  *\n- * (1) .gitattribute file of the same directory;\n- * (2) .gitattribute file of the parent directory if (1) does not have\n+ * (1) .gitattributes file of the same directory;\n+ * (2) .gitattributes file of the parent directory if (1) does not have\n  *      any match; this goes recursively upwards, just like .gitignore.\n  * (3) $GIT_DIR/info/attributes, which overrides both of the above.\n  *\n  * In the same file, later entries override the earlier match, so in the\n  * global list, we would have entries from info/attributes the earliest\n- * (reading the file from top to bottom), .gitattribute of the root\n+ * (reading the file from top to bottom), .gitattributes of the root\n  * directory (again, reading the file from top to bottom) down to the\n  * current directory, and then scan the list backwards to find the first match.\n  * This is exactly the same as what is_excluded() does in dir.c to deal with\n@@ -899,7 +899,7 @@ static void prepare_attr_stack(const struct index_state *istate,\n \t * set of attribute definitions, followed by the contents\n \t * of $(prefix)/etc/gitattributes and a file specified by\n \t * core.attributesfile.  Then, contents from\n-\t * .gitattribute files from directories closer to the\n+\t * .gitattributes files from directories closer to the\n \t * root to the ones in deeper directories are pushed\n \t * to the stack.  Finally, at the very top of the stack\n \t * we always keep the contents of $GIT_DIR/info/attributes.\n\n-- \n\n========================================================================\nRobert P. J. Day                                 Ottawa, Ontario, CANADA\n                  http://crashcourse.ca/dokuwiki\n\nTwitter:                                       http://twitter.com/rpjday\nLinkedIn:                               http://ca.linkedin.com/in/rpjday\n========================================================================\n"}]}