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 * A credential helper for Win32 to allow access to the keychain of 25 the logged-in user has been added. 26 27 * "git cherry-pick" learned the "--allow-empty-message" option to 28 allow it to replay a commit without any log message. 29 30 * "git daemon" learned the "--access-hook" option to allow an 31 external command to decline service based on the client address, 32 repository path, etc. 33 34 * "git difftool --dir-diff" learned to use symbolic links to prepare 35 temporary copy of the working tree when available. 36 37 * "git grep" learned to use a non-standard pattern type by default if 38 a configuration variable tells it to. 39 40Foreign Interface 41 42 * "git svn" has been updated to work with SVN 1.7. 43 44Performance, Internal Implementation, etc. (please report possible regressions) 45 46 * The "check-docs" build target has been updated and greatly 47 simplified. 48 49 * The documentation in the TeXinfo format was using indented output 50 for materials meant to be examples that are better typeset in 51 monospace. 52 53 * Compatibility wrapper to learn the maximum number of file 54 descriptors we can open around sysconf(_SC_OPEN_MAX) and 55 getrlimit(RLIMIT_NO_FILE) has been introduced for portability. 56 57 * Compatibility wrapper around some mkdir(2) implementations that 58 reject parameter with trailing slash has been introduced. 59 60Also contains minor documentation updates and code clean-ups. 61 62 63Fixes since v1.7.12 64------------------- 65 66Unless otherwise noted, all the fixes since v1.7.12 in the 67maintenance track are contained in this release (see release notes 68to them for details). 69 70 * The exit status code from "git config" was way overspecified while 71 being incorrect. The implementation has been updated to give the 72 documented status for a case that was documented, and introduce a 73 new code for "all other errors". 74 (merge 9409c7a jc/maint-config-exit-status later to maint). 75 76 * "git foo" errored out with "Not a directory" when the user had a 77 non-directory on $PATH, and worse yet it masked an alias "foo" from 78 running. (merge a785508 jc/maint-sane-execvp-notdir later to 79 maint). 80 81 * The interactive prompt "git send-email" gives was error prone. It 82 asked "What e-mail address do you want to use?" with the address it 83 guessed (correctly) the user would want to use in its prompt, 84 tempting the user to say "y". But the response was taken as "No, 85 please use 'y' as the e-mail address instead", which is most 86 certainly not what the user meant. 87 (merge 51bbccf jc/send-email-reconfirm later to maint). 88 89 * "git stash apply/pop" did not trigger "rerere" upon conflicts 90 unlike other mergy operations. 91 (merge 743bf6d ph/stash-rerere later to maint). 92 93 * "git submodule update -f" did not update paths in the working tree 94 that has local changes. 95 (merge 01d4721 sz/submodule-force-update later to maint). 96 97 * We used curl_easy_strerror() without checking version of cURL, 98 breaking the build for versions before curl 7.12.0. 99 (merge 4246b0b js/no-curl-easy-strerror-on-old-curl later to maint). 100 101 * Code to work around MacOS X UTF-8 gotcha has been cleaned up. 102 (merge 9a27f96 rr/precompose-utf8-cleanup later to maint). 103 104 * Documentation for the configuration file format had a confusing 105 example. 106 (merge d1e1fe7 mh/maint-config-doc-proxy-command later to maint). 107 108 * "git submodule <cmd> path" did not error out when the path to the 109 submodule was misspelt. 110 (merge be9d0a3 hv/submodule-path-unmatch later to maint). 111 112 * Some capabilities were asked by fetch-pack even when upload-pack 113 did not advertise that they are available. fetch-pack has been 114 fixed not to do so. 115 116 * The reflog entries left by "git rebase" and "git rebase -i" were 117 inconsistent (the interactive one gave an abbreviated object name). 118 (merge 1af221e mg/rebase-i-onto-reflog-in-full later to maint). 119 120 * When the user exports a non-default IFS without HT, scripts that 121 rely on being able to parse "ls-files -s | while read a b c..." 122 start to fail. Protect them from such a misconfiguration. 123 (merge 785063e jc/maint-protect-sh-from-ifs later to maint). 124 125 * "git prune" without "-v" used to warn about leftover temporary 126 files (which is an indication of an earlier aborted operation). 127 (merge 90b29cb bc/prune-info later to maint). 128 129 * When "git push" triggered the automatic gc on the receiving end, a 130 message from "git prune" that said it was removing cruft leaked to 131 the standard output, breaking the communication protocol. 132 (merge 4b7f2fa bc/receive-pack-stdout-protection later to maint). 133 134 * "git diff" had a confusion between taking data from a path in the 135 working tree and taking data from an object that happens to have 136 name 0{40} recorded in a tree. 137 (merge c479d14 jk/maint-null-in-trees later to maint). 138 139 * The output from "git diff -B" for a file that ends with an 140 incomplete line did not put "\ No newline..." on a line of its own. 141 142 * "git send-email" did not unquote encoded words that appear on the 143 header correctly, and lost "_" from strings. 144 (merge b622d4d tr/maint-send-email-2047 later to maint). 145 146 * When the user gives an argument that can be taken as both a 147 revision name and a pathname without disambiguating with "--", we 148 used to give a help message "Use '--' to separate". The message 149 has been clarified to show where that '--' goes on the command 150 line. 151 (merge 4d4b573 mm/die-with-dashdash-help later to maint). 152 153 * "gitweb" when used with PATH_INFO failed to notice directories with 154 SP (and other characters that need URL-style quoting) in them. 155 (merge cacfc09 js/gitweb-path-info-unquote later to maint).