{"thread":{"id":"51218","subject":"[PATCH] RelNotes: minor typo fixes in 2.22.0 draft","startedAt":"2019-06-01T15:51:17Z","lastAt":"2019-06-03T18:06:13Z","messageCount":2,"participants":["Todd Zullinger","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"376532","messageId":"20190601155106.GK3654@pobox.com","threadId":"51218","inReplyTo":null,"subject":"[PATCH] RelNotes: minor typo fixes in 2.22.0 draft","fromName":"Todd Zullinger","fromEmail":"tmz@pobox.com","sentAt":"2019-06-01T15:51:06Z","receivedAt":"2019-06-01T15:51:17Z","isPatch":true,"sender":{"key":"tmz@pobox.com","avatar":"https://avatars.githubusercontent.com/u/806319?v=4"},"body":"Signed-off-by: Todd Zullinger <tmz@pobox.com>\n---\nThese are all just minor typos I noticed while reading the\nrelease notes.\n\nI did find the first entry on the checkout --no-overlay read\na bit strangely with the multiple \"out's\" in '... checking\nout paths out ...'.  Is it any easier to read with:\n\n    * \"git checkout --no-overlay\" can be used to trigger a new mode of\n  -   checking out paths out of the tree-ish, that allows paths that\n  +   checking out paths from the tree-ish, which allows paths that\n      match the pathspec that are in the current index and working tree\n      and are not in the tree-ish.\n\n? (There's any number of other ways to drop one of the\n\"out's\" [and similarly replaces a \"that\" with \"which\"] in\nthe sentence, of course.  Whether it's worth doing at all is\nreally the question.)\n\n Documentation/RelNotes/2.22.0.txt | 12 ++++++------\n 1 file changed, 6 insertions(+), 6 deletions(-)\n\ndiff --git a/Documentation/RelNotes/2.22.0.txt b/Documentation/RelNotes/2.22.0.txt\nindex 84e1ba6106..5aa4a256ae 100644\n--- a/Documentation/RelNotes/2.22.0.txt\n+++ b/Documentation/RelNotes/2.22.0.txt\n@@ -181,7 +181,7 @@ Performance, Internal Implementation, Development Support etc.\n    been optimized out.\n \n  * Mechanically and systematically drop \"extern\" from function\n-   declarlation.\n+   declaration.\n \n  * The script to aggregate perf result unconditionally depended on\n    libjson-perl even though it did not have to, which has been\n@@ -270,7 +270,7 @@ Fixes since v2.21\n  * On platforms where \"git fetch\" is killed with SIGPIPE (e.g. OSX),\n    the upload-pack that runs on the other end that hangs up after\n    detecting an error could cause \"git fetch\" to die with a signal,\n-   which led to a flakey test.  \"git fetch\" now ignores SIGPIPE during\n+   which led to a flaky test.  \"git fetch\" now ignores SIGPIPE during\n    the network portion of its operation (this is not a problem as we\n    check the return status from our write(2)s).\n    (merge 143588949c jk/no-sigpipe-during-network-transport later to maint).\n@@ -358,7 +358,7 @@ Fixes since v2.21\n    (merge b5a0bd694c nd/read-tree-reset-doc later to maint).\n \n  * Code clean-up around a much-less-important-than-it-used-to-be\n-   update_server_info() funtion.\n+   update_server_info() function.\n    (merge b3223761c8 jk/server-info-rabbit-hole later to maint).\n \n  * The message given when \"git commit -a <paths>\" errors out has been\n@@ -450,7 +450,7 @@ Fixes since v2.21\n  * When given a tag that points at a commit-ish, \"git replace --graft\"\n    failed to peel the tag before writing a replace ref, which did not\n    make sense because the old graft mechanism the feature wants to\n-   mimick only allowed to replace one commit object with another.\n+   mimic only allowed to replace one commit object with another.\n    This has been fixed.\n    (merge ee521ec4cb cc/replace-graft-peel-tags later to maint).\n \n@@ -500,7 +500,7 @@ Fixes since v2.21\n    conflicts are resolved in working tree *.h files but before the\n    resolved results are added to the index.  This has been corrected.\n \n- * \"git chery-pick\" (and \"revert\" that shares the same runtime engine)\n+ * \"git cherry-pick\" (and \"revert\" that shares the same runtime engine)\n    that deals with multiple commits got confused when the final step\n    gets stopped with a conflict and the user concluded the sequence\n    with \"git commit\".  Attempt to fix it by cleaning up the state\n@@ -535,7 +535,7 @@ Fixes since v2.21\n    todo-list \"rebase -i -r\" uses should not be shown as a hex object\n    name.\n \n- * A prerequiste check in the test suite to see if a working jgit is\n+ * A prerequisite check in the test suite to see if a working jgit is\n    available was made more robust.\n    (merge abd0f28983 tz/test-lib-check-working-jgit later to maint).\n \n-- \nTodd\n"},{"id":"376591","messageId":"xmqqo93ev90y.fsf@gitster-ct.c.googlers.com","threadId":"51218","inReplyTo":"20190601155106.GK3654@pobox.com","subject":"Re: [PATCH] RelNotes: minor typo fixes in 2.22.0 draft","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2019-06-03T18:06:05Z","receivedAt":"2019-06-03T18:06:13Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Todd Zullinger <tmz@pobox.com> writes:\n\n> Signed-off-by: Todd Zullinger <tmz@pobox.com>\n> ---\n> These are all just minor typos I noticed while reading the\n> release notes.\n>\n> I did find the first entry on the checkout --no-overlay read\n> a bit strangely with the multiple \"out's\" in '... checking\n> out paths out ...'.\n\nAh, of courese, \"checking paths out of the tree-ish\" was what I\nmeant to say, as I find \"checkout\" (or worse \"check-out\", or even\nworse \"check out\") used as a verb a bit too techy.\n\nThanks for all other typofixes.\n"}]}