···8899 * "git rebase" uses a different backend that is based on the 'merge'
1010 machinery by default. There are a few known differences in the
1111- behaviour from the traditional machniery based on patch+apply.
1111+ behaviour from the traditional machinery based on patch+apply.
12121313 If your workflow is negatively affected by this change, please
1414 report it to git@vger.kernel.org so that we can take a look into
···6363 * "git rm" and "git stash" learns the new "--pathspec-from-file"
6464 option.
65656666- * "git am --short-current-patch" is a way to show the piece of e-mail
6666+ * "git am --show-current-patch" is a way to show the piece of e-mail
6767 for the stopped step, which is not suitable to directly feed "git
6868 apply" (it is designed to be a good "git am" input). It learned a
6969 new option to show only the patch part.
···7979 with tabs.
80808181 * The test-lint machinery knew to check "VAR=VAL shell_function"
8282- construct, but did not check "VAR= shell_funciton", which has been
8282+ construct, but did not check "VAR= shell_function", which has been
8383 corrected.
84848585 * Replace "git config --bool" calls with "git config --type=bool" in
···229229 * Unhelpful warning messages during documentation build have been squelched.
230230231231 * "git rebase -i" identifies existing commits in its todo file with
232232- their abbreviated object name, which could become ambigous as it
232232+ their abbreviated object name, which could become ambiguous as it
233233 goes to create new commits, and has a mechanism to avoid ambiguity
234234 in the main part of its execution. A few other cases however were
235235 not covered by the protection against ambiguity, which has been