1Git v1.8.2 Release Notes 2======================== 3 4Backward compatibility notes 5---------------------------- 6 7In the upcoming major release (tentatively called 1.8.2), we will 8change the behavior of the "git push" command. 9 10When "git push [$there]" does not say what to push, we have used the 11traditional "matching" semantics so far (all your branches were sent 12to the remote as long as there already are branches of the same name 13over there). We will use the "simple" semantics that pushes the 14current branch to the branch with the same name, only when the current 15branch is set to integrate with that remote branch. There is a user 16preference configuration variable "push.default" to change this. 17 18 19Updates since v1.8.1 20-------------------- 21 22UI, Workflows & Features 23 24 * Initial ports to QNX and z/OS UNIX System Services have started. 25 26 * Output from the tests is coloured using "green is okay, yellow is 27 questionable, red is bad and blue is informative" scheme. 28 29 * In bare repositories, "git shortlog" and other commands now read 30 mailmap files from the tip of the history, to help running these 31 tools in server settings. 32 33 * Color specifiers, e.g. "%C(blue)Hello%C(reset)", used in the 34 "--format=" option of "git log" and friends can be disabled when 35 the output is not sent to a terminal by prefixing them with 36 "auto,", e.g. "%C(auto,blue)Hello%C(auto,reset)". 37 38 * Scripts can ask Git that wildcard patterns in pathspecs they give do 39 not have any significance, i.e. take them as literal strings. 40 41 * The pathspec code learned to grok "foo/**/bar" as a pattern that 42 matches "bar" in 0-or-more levels of subdirectory in "foo". 43 44 * "git cherry-pick" can be used to replay a root commit to an unborn 45 branch. 46 47 * "git fetch --mirror" and fetch that uses other forms of refspec 48 with wildcard used to attempt to update a symbolic ref that match 49 the wildcard on the receiving end, which made little sense (the 50 real ref that is pointed at by the symbolic ref would be updated 51 anyway). Symbolic refs no longer are affected by such a fetch. 52 53 * "git format-patch" now detects more cases in which a whole branch 54 is being exported, and uses the description for the branch, when 55 asked to write a cover letter for the series. 56 57 * "git push" now requires "-f" to update a tag, even if it is a 58 fast-forward, as tags are meant to be fixed points. 59 60 * When "git rebase" fails to generate patches to be applied (e.g. due 61 to oom), it failed to detect the failure and instead behaved as if 62 there were nothing to do. A workaround to use a temporary file has 63 been applied, but we probably would want to revisit this later, as 64 it hurts the common case of not failing at all. 65 66 * "git submodule" started learning a new mode to integrate with the 67 tip of the remote branch (as opposed to integrating with the commit 68 recorded in the superproject's gitlink). 69 70 71Foreign Interface 72 73 * "git fast-export" has been updated for its use in the context of 74 the remote helper interface. 75 76 * A new remote helper to interact with bzr has been added to contrib/. 77 78 79Performance, Internal Implementation, etc. 80 81 * "git fsck" has been taught to be pickier about entries in tree 82 objects that should not be there, e.g. ".", ".git", and "..". 83 84 * Matching paths with common forms of pathspecs that contain wildcard 85 characters has been optimized further. 86 87 * The implementation of "imap-send" has been updated to reuse xml 88 quoting code from http-push codepath. 89 90 * There is a simple-minded checker for the test scripts in t/ 91 directory to catch most common mistakes (it is not enabled by 92 default). 93 94 95Also contains minor documentation updates and code clean-ups. 96 97 98Fixes since v1.8.1 99------------------ 100 101Unless otherwise noted, all the fixes since v1.8.1 in the maintenance 102track are contained in this release (see release notes to them for 103details). 104 105 * An element on GIT_CEILING_DIRECTORIES list that does not name the 106 real path to a directory (i.e. a symbolic link) could have caused 107 the GIT_DIR discovery logic to escape the ceiling. 108 (merge 059b379 mh/ceiling later to maint). 109 110 * When attempting to read the XDG-style $HOME/.config/git/config and 111 finding that $HOME/.config/git is a file, we gave a wrong error 112 message, instead of treating the case as "a custom config file does 113 not exist there" and moving on. 114 (merge 8f2bbe4 jn/warn-on-inaccessible-loosen later to maint). 115 116 * The behaviour visible to the end users was confusing, when they 117 attempt to kill a process spawned in the editor that was in turn 118 launched by Git with SIGINT (or SIGQUIT), as Git would catch that 119 signal and die. We ignore these signals now. 120 (merge 1250857 pf/editor-ignore-sigint later to maint). 121 122 * After failing to create a temporary file using mkstemp(), failing 123 pathname was not reported correctly on some platforms. 124 (merge f7be59b jc/mkstemp-more-careful-error-reporting later to maint). 125 126 * The attribute mechanism didn't allow limiting attributes to be 127 applied to only a single directory itself with "path/" like the 128 exclude mechanism does. 129 (merge 94bc671 ja/directory-attrs later to maint). 130 131 * "git apply" misbehaved when fixing whitespace breakages by removing 132 excess trailing blank lines. 133 (merge 5de7166 jc/apply-trailing-blank-removal later to maint). 134 135 * A tar archive created by "git archive" recorded a directory in a 136 way that made NetBSD's implementation of "tar" sometimes unhappy. 137 (merge 22f0dcd rs/leave-base-name-in-name-field-of-tar later to maint). 138 139 * When "git clone --separate-git-dir=$over_there" is interrupted, it 140 failed to remove the real location of the $GIT_DIR it created. 141 This was most visible when interrupting a submodule update. 142 (merge 9be1980 jl/interrupt-clone-remove-separate-git-dir later to maint). 143 144 * The way "git svn" asked for password using SSH_ASKPASS and 145 GIT_ASKPASS was not in line with the rest of the system. 146 (merge e9263e4 ss/svn-prompt later to maint). 147 148 * The --graph code fell into infinite loop when asked to do what the 149 code did not expect. 150 (merge 656197a mk/maint-graph-infinity-loop later to maint). 151 152 * http transport was wrong to ask for the username when the 153 authentication is done by certificate identity. 154 (merge 75e9a40 rb/http-cert-cred-no-username-prompt later to maint). 155 156 * "git pack-refs" that ran in parallel to another process that 157 created new refs had a nasty race. 158 (merge b3f1280 jk/repack-ref-racefix later to maint). 159 160 * After "git add -N" and then writing a tree object out of the 161 index, the cache-tree data structure got corrupted. 162 (merge eec3e7e nd/invalidate-i-t-a-cache-tree later to maint). 163 164 * "git merge --no-edit" computed who were involved in the work done 165 on the side branch, even though that information is to be discarded 166 without getting seen in the editor. 167 (merge 9bcbb1c jc/maint-fmt-merge-msg-no-edit-lose-credit later to maint). 168 169 * "git merge" started calling prepare-commit-msg hook like "git 170 commit" does some time ago, but forgot to pay attention to the exit 171 status of the hook. 172 (merge 3e4141d ap/merge-stop-at-prepare-commit-msg-failure later to maint). 173 174 * "gitweb", when sorting by age to show repositories with new 175 activities first, used to sort repositories with absolutely 176 nothing in it early, which was not very useful. 177 (merge 28dae18 md/gitweb-sort-by-age later to maint). 178 179 * "gitweb"'s code to sanitize control characters before passing it to 180 "highlight" filter lost known-to-be-safe control characters by 181 mistake. 182 (merge 0e901d2 os/gitweb-highlight-uncaptured later to maint). 183 184 * When a line to be wrapped has a solid run of non space characters 185 whose length exactly is the wrap width, "git shortlog -w" failed 186 to add a newline after such a line. 187 (merge e0db176 sp/shortlog-missing-lf later to maint). 188 189 * Some shells do not behave correctly when IFS is unset; work it 190 around by explicitly setting it to the default value. 191 (merge 393050c jc/maint-fbsd-sh-ifs-workaround later to maint). 192 193 * Some scripted programs written in Python did not get updated when 194 PYTHON_PATH changed. 195 (cherry-pick 96a4647fca54031974cd6ad1 later to maint). 196 197 * When autoconf is used, any build on a different commit always ran 198 "config.status --recheck" even when unnecessary. 199 (merge 1226504 jn/less-reconfigure later to maint). 200 201 * We have been carrying a translated and long-unmaintained copy of an 202 old version of the tutorial; removed. 203 (merge 0a85441 ta/remove-stale-translated-tut later to maint). 204 205 * t4014, t9502 and t0200 tests had various portability issues that 206 broke on OpenBSD. 207 (merge 27f6342 jc/maint-test-portability later to maint). 208 209 * t9020 and t3600 tests had various portability issues. 210 (merge 5a02966 jc/test-portability later to maint). 211 212 * t9200 runs "cvs init" on a directory that already exists, but a 213 platform can configure this fail for the current user (e.g. you 214 need to be in the cvsadmin group on NetBSD 6.0). 215 (merge 8666df0 jc/test-cvs-no-init-in-existing-dir later to maint). 216 217 * t9020 and t9810 had a few non-portable shell script construct. 218 (merge 2797914 tb/test-t9020-no-which later to maint). 219 (merge 6f4e505 tb/test-t9810-no-sed-i later to maint).