1Git v1.8.0 Release Notes 2======================== 3 4Backward compatibility notes 5---------------------------- 6 7In the next major release, we will change the behaviour of the "git 8push" command. When "git push [$there]" does not say what to push, we 9have used the traditional "matching" semantics (all your branches were 10sent to the remote as long as there already are branches of the same 11name over there). We will use the "simple" semantics, that pushes the 12current branch to the branch with the same name only when the current 13branch is set to integrate with that remote branch. There is a user 14preference configuration variable "push.default" to change this, and 15"git push" will warn about the upcoming change until you set this 16variable. 17 18 19Updates since v1.7.12 20--------------------- 21 22UI, Workflows & Features 23 24 * "git difftool --dir-diff" learned to use symbolic links to prepare 25 temporary copy of the working tree when available. 26 27 * "git grep" learned to use a non-standard pattern type by default if 28 a configuration variable tells it to. 29 30Foreign Interface 31 32 * "git svn" has been updated to work with SVN 1.7. 33 34 35Performance, Internal Implementation, etc. (please report possible regressions) 36 37 * The "check-docs" build target has been updated and greatly 38 simplified. 39 40 * The documentation in the TeXinfo format was using indented output 41 for materials meant to be examples that are better typeset in 42 monospace. 43 44Also contains minor documentation updates and code clean-ups. 45 46 47Fixes since v1.7.12 48------------------- 49 50Unless otherwise noted, all the fixes since v1.7.12 in the 51maintenance track are contained in this release (see release notes 52to them for details). 53 54 55 * When "git push" triggered the automatic gc on the receiving end, a 56 message from "git prune" that said it was removing cruft leaked to 57 the standard output, breaking the communication protocol. 58 (merge 4b7f2fa bc/receive-pack-stdout-protection later to maint). 59 60 * "git diff" had a confusion between taking data from a path in the 61 working tree and taking data from an object that happens to have 62 name 0{40} recorded in a tree. 63 (merge c479d14 jk/maint-null-in-trees later to maint). 64 65 * The output from "git diff -B" for a file that ends with an 66 incomplete line did not put "\ No newline..." on a line of its own. 67 68 * "git send-email" did not unquote encoded words that appear on the 69 header correctly, and lost "_" from strings. 70 (merge b622d4d tr/maint-send-email-2047 later to maint). 71 72 * When the user gives an argument that can be taken as both a 73 revision name and a pathname without disambiguating with "--", we 74 used to give a help message "Use '--' to separate". The message 75 has been clarified to show where that '--' goes on the command 76 line. 77 (merge 4d4b573 mm/die-with-dashdash-help later to maint). 78 79 * "gitweb" when used with PATH_INFO failed to notice directories with 80 SP (and other characters that need URL-style quoting) in them. 81 (merge cacfc09 js/gitweb-path-info-unquote later to maint).