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