{"thread":{"id":"18711","subject":"[PATCH] doc/git-pack-refs: fix two grammar issues","startedAt":"2009-04-04T10:35:22Z","lastAt":"2009-04-04T10:35:22Z","messageCount":1,"participants":["Markus Heidelberg"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"110331","messageId":"200904041235.23310.markus.heidelberg@web.de","threadId":"18711","inReplyTo":null,"subject":"[PATCH] doc/git-pack-refs: fix two grammar issues","fromName":"Markus Heidelberg","fromEmail":"markus.heidelberg@web.de","sentAt":"2009-04-04T10:35:22Z","receivedAt":"2009-04-04T10:35:22Z","isPatch":true,"sender":{"key":"markus.heidelberg@web.de","avatar":"https://avatars.githubusercontent.com/u/6334512?v=4"},"body":"\nSigned-off-by: Markus Heidelberg <markus.heidelberg@web.de>\n---\n Documentation/git-pack-refs.txt |    4 ++--\n 1 files changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-pack-refs.txt b/Documentation/git-pack-refs.txt\nindex a5244d3..1ee99c2 100644\n--- a/Documentation/git-pack-refs.txt\n+++ b/Documentation/git-pack-refs.txt\n@@ -26,7 +26,7 @@ problem by stashing the refs in a single file,\n traditional `$GIT_DIR/refs` hierarchy, it is looked up in this\n file and used if found.\n \n-Subsequent updates to branches always creates new file under\n+Subsequent updates to branches always create new files under\n `$GIT_DIR/refs` hierarchy.\n \n A recommended practice to deal with a repository with too many\n@@ -35,7 +35,7 @@ occasionally run `git pack-refs \\--prune`.  Tags are by\n definition stationary and are not expected to change.  Branch\n heads will be packed with the initial `pack-refs --all`, but\n only the currently active branch heads will become unpacked,\n-and next `pack-refs` (without `--all`) will leave them\n+and the next `pack-refs` (without `--all`) will leave them\n unpacked.\n \n \n-- \n1.6.2.1.428.g41b20c\n"}]}