···89 * "git rebase" uses a different backend that is based on the 'merge'
10 machinery by default. There are a few known differences in the
11- behaviour from the traditional machniery based on patch+apply.
1213 If your workflow is negatively affected by this change, please
14 report it to git@vger.kernel.org so that we can take a look into
···63 * "git rm" and "git stash" learns the new "--pathspec-from-file"
64 option.
6566- * "git am --short-current-patch" is a way to show the piece of e-mail
67 for the stopped step, which is not suitable to directly feed "git
68 apply" (it is designed to be a good "git am" input). It learned a
69 new option to show only the patch part.
···79 with tabs.
8081 * The test-lint machinery knew to check "VAR=VAL shell_function"
82- construct, but did not check "VAR= shell_funciton", which has been
83 corrected.
8485 * Replace "git config --bool" calls with "git config --type=bool" in
···229 * Unhelpful warning messages during documentation build have been squelched.
230231 * "git rebase -i" identifies existing commits in its todo file with
232- their abbreviated object name, which could become ambigous as it
233 goes to create new commits, and has a mechanism to avoid ambiguity
234 in the main part of its execution. A few other cases however were
235 not covered by the protection against ambiguity, which has been
···89 * "git rebase" uses a different backend that is based on the 'merge'
10 machinery by default. There are a few known differences in the
11+ behaviour from the traditional machinery based on patch+apply.
1213 If your workflow is negatively affected by this change, please
14 report it to git@vger.kernel.org so that we can take a look into
···63 * "git rm" and "git stash" learns the new "--pathspec-from-file"
64 option.
6566+ * "git am --show-current-patch" is a way to show the piece of e-mail
67 for the stopped step, which is not suitable to directly feed "git
68 apply" (it is designed to be a good "git am" input). It learned a
69 new option to show only the patch part.
···79 with tabs.
8081 * The test-lint machinery knew to check "VAR=VAL shell_function"
82+ construct, but did not check "VAR= shell_function", which has been
83 corrected.
8485 * Replace "git config --bool" calls with "git config --type=bool" in
···229 * Unhelpful warning messages during documentation build have been squelched.
230231 * "git rebase -i" identifies existing commits in its todo file with
232+ their abbreviated object name, which could become ambiguous as it
233 goes to create new commits, and has a mechanism to avoid ambiguity
234 in the main part of its execution. A few other cases however were
235 not covered by the protection against ambiguity, which has been