| blob | e45788ef3e15e55e2e884adeaa873b9cb8d59942 |
1 Git v1.8.0 Release Notes
2 ========================
4 Backward compatibility notes
5 ----------------------------
7 In the next major release, we will change the behaviour of the "git
8 push" command. When "git push [$there]" does not say what to push, we
9 have used the traditional "matching" semantics (all your branches were
10 sent to the remote as long as there already are branches of the same
11 name over there). We will use the "simple" semantics, that pushes the
12 current branch to the branch with the same name only when the current
13 branch is set to integrate with that remote branch. There is a user
14 preference configuration variable "push.default" to change this, and
15 "git push" will warn about the upcoming change until you set this
16 variable.
19 Updates since v1.7.12
20 ---------------------
22 UI, Workflows & Features
24 * A credential helper for Win32 to allow access to the keychain of
25 the logged-in user has been added.
27 * "git difftool --dir-diff" learned to use symbolic links to prepare
28 temporary copy of the working tree when available.
30 * "git grep" learned to use a non-standard pattern type by default if
31 a configuration variable tells it to.
33 Foreign Interface
35 * "git svn" has been updated to work with SVN 1.7.
37 Performance, Internal Implementation, etc. (please report possible regressions)
39 * The "check-docs" build target has been updated and greatly
40 simplified.
42 * The documentation in the TeXinfo format was using indented output
43 for materials meant to be examples that are better typeset in
44 monospace.
46 Also contains minor documentation updates and code clean-ups.
49 Fixes since v1.7.12
50 -------------------
52 Unless otherwise noted, all the fixes since v1.7.12 in the
53 maintenance track are contained in this release (see release notes
54 to them for details).
56 * Code to work around MacOS X UTF-8 gotcha has been cleaned up.
57 (merge 9a27f96 rr/precompose-utf8-cleanup later to maint).
59 * Documentation for the configuration file format had a confusing
60 example.
61 (merge d1e1fe7 mh/maint-config-doc-proxy-command later to maint).
63 * "git submodule <cmd> path" did not error out when the path to the
64 submodule was misspelt.
65 (merge be9d0a3 hv/submodule-path-unmatch later to maint).
67 * Some capabilities were asked by fetch-pack even when upload-pack
68 did not advertise that they are available. fetch-pack has been
69 fixed not to do so.
71 * The reflog entries left by "git rebase" and "git rebase -i" were
72 inconsistent (the interactive one gave an abbreviated object name).
73 (merge 1af221e mg/rebase-i-onto-reflog-in-full later to maint).
75 * When the user exports a non-default IFS without HT, scripts that
76 rely on being able to parse "ls-files -s | while read a b c..."
77 start to fail. Protect them from such a misconfiguration.
78 (merge 785063e jc/maint-protect-sh-from-ifs later to maint).
80 * "git prune" without "-v" used to warn about leftover temporary
81 files (which is an indication of an earlier aborted operation).
82 (merge 90b29cb bc/prune-info later to maint).
84 * When "git push" triggered the automatic gc on the receiving end, a
85 message from "git prune" that said it was removing cruft leaked to
86 the standard output, breaking the communication protocol.
87 (merge 4b7f2fa bc/receive-pack-stdout-protection later to maint).
89 * "git diff" had a confusion between taking data from a path in the
90 working tree and taking data from an object that happens to have
91 name 0{40} recorded in a tree.
92 (merge c479d14 jk/maint-null-in-trees later to maint).
94 * The output from "git diff -B" for a file that ends with an
95 incomplete line did not put "\ No newline..." on a line of its own.
97 * "git send-email" did not unquote encoded words that appear on the
98 header correctly, and lost "_" from strings.
99 (merge b622d4d tr/maint-send-email-2047 later to maint).
101 * When the user gives an argument that can be taken as both a
102 revision name and a pathname without disambiguating with "--", we
103 used to give a help message "Use '--' to separate". The message
104 has been clarified to show where that '--' goes on the command
105 line.
106 (merge 4d4b573 mm/die-with-dashdash-help later to maint).
108 * "gitweb" when used with PATH_INFO failed to notice directories with
109 SP (and other characters that need URL-style quoting) in them.
110 (merge cacfc09 js/gitweb-path-info-unquote later to maint).