| 1 | Git v1.8.3.2 Release Notes |
| 2 | ========================== |
| 3 | |
| 4 | Fixes since v1.8.3.1 |
| 5 | -------------------- |
| 6 | |
| 7 | * Cloning with "git clone --depth N" while fetch.fsckobjects (or |
| 8 | transfer.fsckobjects) is set to true did not tell the cut-off |
| 9 | points of the shallow history to the process that validates the |
| 10 | objects and the history received, causing the validation to fail. |
| 11 | |
| 12 | * "git checkout foo" DWIMs the intended "upstream" and turns it into |
| 13 | "git checkout -t -b foo remotes/origin/foo". This codepath has been |
| 14 | updated to correctly take existing remote definitions into account. |
| 15 | |
| 16 | * "git fetch" into a shallow repository from a repository that does |
| 17 | not know about the shallow boundary commits (e.g. a different fork |
| 18 | from the repository the current shallow repository was cloned from) |
| 19 | did not work correctly. |
| 20 | |
| 21 | * "git subtree" (in contrib/) had one codepath with loose error |
| 22 | checks to lose data at the remote side. |
| 23 | |
| 24 | * "git log --ancestry-path A...B" did not work as expected, as it did |
| 25 | not pay attention to the fact that the merge base between A and B |
| 26 | was the bottom of the range being specified. |
| 27 | |
| 28 | * "git diff -c -p" was not showing a deleted line from a hunk when |
| 29 | another hunk immediately begins where the earlier one ends. |
| 30 | |
| 31 | * "git merge @{-1}~22" was rewritten to "git merge frotz@{1}~22" |
| 32 | incorrectly when your previous branch was "frotz" (it should be |
| 33 | rewritten to "git merge frotz~22" instead). |
| 34 | |
| 35 | * "git commit --allow-empty-message -m ''" should not start an |
| 36 | editor. |
| 37 | |
| 38 | * "git push --[no-]verify" was not documented. |
| 39 | |
| 40 | * An entry for "file://" scheme in the enumeration of URL types Git |
| 41 | can take in the HTML documentation was made into a clickable link |
| 42 | by mistake. |
| 43 | |
| 44 | * zsh prompt script that borrowed from bash prompt script did not |
| 45 | work due to slight differences in array variable notation between |
| 46 | these two shells. |
| 47 | |
| 48 | * The bash prompt code (in contrib/) displayed the name of the branch |
| 49 | being rebased when "rebase -i/-m/-p" modes are in use, but not the |
| 50 | plain vanilla "rebase". |
| 51 | |
| 52 | * "git push $there HEAD:branch" did not resolve HEAD early enough, so |
| 53 | it was easy to flip it around while push is still going on and push |
| 54 | out a branch that the user did not originally intended when the |
| 55 | command was started. |
| 56 | |
| 57 | * "difftool --dir-diff" did not copy back changes made by the |
| 58 | end-user in the diff tool backend to the working tree in some |
| 59 | cases. |