{"thread":{"id":"53628","subject":"[PATCH] t/README: avoid poor-man's small caps GIT","startedAt":"2020-06-07T09:48:40Z","lastAt":"2020-06-07T09:48:40Z","messageCount":1,"participants":["Denton Liu"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"399240","messageId":"6cbd5c34b5cba6087cf8ee900e3a8285d2af2603.1591523289.git.liu.denton@gmail.com","threadId":"53628","inReplyTo":null,"subject":"[PATCH] t/README: avoid poor-man's small caps GIT","fromName":"Denton Liu","fromEmail":"liu.denton@gmail.com","sentAt":"2020-06-07T09:48:26Z","receivedAt":"2020-06-07T09:48:40Z","isPatch":true,"sender":{"key":"liu.denton@gmail.com","avatar":"https://avatars.githubusercontent.com/u/9620836?v=4"},"body":"In 48a8c26c62 (Documentation: avoid poor-man's small caps GIT,\n2013-01-21), the documentation was amended to spell Git's name as Git\nwhen talking about the system as a whole. However, t/README was skipped\nover when the treatment was applied.\n\nBring t/README into conformance with the CodingGuidelines by casing\n\"Git\" properly.\n\nWhile we're at it, fix a small typo. Change \"the git internal\" to \"the\nGit internals\".\n\nSigned-off-by: Denton Liu <liu.denton@gmail.com>\n---\n t/README | 14 +++++++-------\n 1 file changed, 7 insertions(+), 7 deletions(-)\n\ndiff --git a/t/README b/t/README\nindex cf863837ab..70ec61cf88 100644\n--- a/t/README\n+++ b/t/README\n@@ -1,7 +1,7 @@\n-Core GIT Tests\n+Core Git Tests\n ==============\n \n-This directory holds many test scripts for core GIT tools.  The\n+This directory holds many test scripts for core Git tools.  The\n first part of this short document describes how to run the tests\n and read their output.\n \n@@ -1117,21 +1117,21 @@ Tips for Writing Tests\n As with any programming projects, existing programs are the best\n source of the information.  However, do _not_ emulate\n t0000-basic.sh when writing your tests.  The test is special in\n-that it tries to validate the very core of GIT.  For example, it\n+that it tries to validate the very core of Git.  For example, it\n knows that there will be 256 subdirectories under .git/objects/,\n and it knows that the object ID of an empty tree is a certain\n 40-byte string.  This is deliberately done so in t0000-basic.sh\n because the things the very basic core test tries to achieve is\n-to serve as a basis for people who are changing the GIT internal\n+to serve as a basis for people who are changing the Git internals\n drastically.  For these people, after making certain changes,\n not seeing failures from the basic test _is_ a failure.  And\n-such drastic changes to the core GIT that even changes these\n+such drastic changes to the core Git that even changes these\n otherwise supposedly stable object IDs should be accompanied by\n an update to t0000-basic.sh.\n \n However, other tests that simply rely on basic parts of the core\n-GIT working properly should not have that level of intimate\n-knowledge of the core GIT internals.  If all the test scripts\n+Git working properly should not have that level of intimate\n+knowledge of the core Git internals.  If all the test scripts\n hardcoded the object IDs like t0000-basic.sh does, that defeats\n the purpose of t0000-basic.sh, which is to isolate that level of\n validation in one place.  Your test also ends up needing\n-- \n2.27.0.107.g134631ef42\n\n"}]}