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 * "git fetch --mirror" and fetch that uses other forms of refspec 42 with wildcard used to attempt to update a symbolic ref that match 43 the wildcard on the receiving end, which made little sense (the 44 real ref that is pointed at by the symbolic ref would be updated 45 anyway). Symbolic refs no longer are affected by such a fetch. 46 47 * "git format-patch" now detects more cases in which a whole branch 48 is being exported, and uses the description for the branch, when 49 asked to write a cover letter for the series. 50 51 * "git push" now requires "-f" to update a tag, even if it is a 52 fast-forward, as tags are meant to be fixed points. 53 54 * "git submodule" started learning a new mode to integrate with the 55 tip of the remote branch (as opposed to integrating with the commit 56 recorded in the superproject's gitlink). 57 58 59Foreign Interface 60 61 * "git fast-export" has been updated for its use in the context of 62 the remote helper interface. 63 64 * A new remote helper to interact with bzr has been added to contrib/. 65 66 67Performance, Internal Implementation, etc. 68 69 * "git fsck" has been taught to be pickier about entries in tree 70 objects that should not be there, e.g. ".", ".git", and "..". 71 72 * Matching paths with common forms of pathspecs that contain wildcard 73 characters has been optimized further. 74 75 * The implementation of "imap-send" has been updated to reuse xml 76 quoting code from http-push codepath. 77 78 79Also contains minor documentation updates and code clean-ups. 80 81 82Fixes since v1.8.1 83------------------ 84 85Unless otherwise noted, all the fixes since v1.8.1 in the maintenance 86track are contained in this release (see release notes to them for 87details). 88 89 * An element on GIT_CEILING_DIRECTORIES list that does not name the 90 real path to a directory (i.e. a symbolic link) could have caused 91 the GIT_DIR discovery logic to escape the ceiling. 92 (merge 059b379 mh/ceiling later to maint). 93 94 * When attempting to read the XDG-style $HOME/.config/git/config and 95 finding that $HOME/.config/git is a file, we gave a wrong error 96 message, instead of treating the case as "a custom config file does 97 not exist there" and moving on. 98 (merge 8f2bbe4 jn/warn-on-inaccessible-loosen later to maint). 99 100 * The behaviour visible to the end users was confusing, when they 101 attempt to kill a process spawned in the editor that was in turn 102 launched by Git with SIGINT (or SIGQUIT), as Git would catch that 103 signal and die. We ignore these signals now. 104 (merge 1250857 pf/editor-ignore-sigint later to maint). 105 106 * After failing to create a temporary file using mkstemp(), failing 107 pathname was not reported correctly on some platforms. 108 (merge f7be59b jc/mkstemp-more-careful-error-reporting later to maint). 109 110 * The attribute mechanism didn't allow limiting attributes to be 111 applied to only a single directory itself with "path/" like the 112 exclude mechanism does. 113 (merge 94bc671 ja/directory-attrs later to maint). 114 115 * "git apply" misbehaved when fixing whitespace breakages by removing 116 excess trailing blank lines. 117 (merge 5de7166 jc/apply-trailing-blank-removal later to maint). 118 119 * The way "git svn" asked for password using SSH_ASKPASS and 120 GIT_ASKPASS was not in line with the rest of the system. 121 (merge e9263e4 ss/svn-prompt later to maint). 122 123 * The --graph code fell into infinite loop when asked to do what the 124 code did not expect. 125 (merge 656197a mk/maint-graph-infinity-loop later to maint). 126 127 * http transport was wrong to ask for the username when the 128 authentication is done by certificate identity. 129 (merge 75e9a40 rb/http-cert-cred-no-username-prompt later to maint). 130 131 * "git pack-refs" that ran in parallel to another process that 132 created new refs had a nasty race. 133 (merge b3f1280 jk/repack-ref-racefix later to maint). 134 135 * After "git add -N" and then writing a tree object out of the 136 index, the cache-tree data structure got corrupted. 137 (merge eec3e7e nd/invalidate-i-t-a-cache-tree later to maint). 138 139 * "git merge" started calling prepare-commit-msg hook like "git 140 commit" does some time ago, but forgot to pay attention to the exit 141 status of the hook. 142 (merge 3e4141d ap/merge-stop-at-prepare-commit-msg-failure later to maint). 143 144 * "gitweb", when sorting by age to show repositories with new 145 activities first, used to sort repositories with absolutely 146 nothing in it early, which was not very useful. 147 (merge 28dae18 md/gitweb-sort-by-age later to maint). 148 149 * "gitweb"'s code to sanitize control characters before passing it to 150 "highlight" filter lost known-to-be-safe control characters by 151 mistake. 152 (merge 0e901d2 os/gitweb-highlight-uncaptured later to maint). 153 154 * When a line to be wrapped has a solid run of non space characters 155 whose length exactly is the wrap width, "git shortlog -w" failed 156 to add a newline after such a line. 157 (merge e0db176 sp/shortlog-missing-lf later to maint). 158 159 * Some shells do not behave correctly when IFS is unset; work it 160 around by explicitly setting it to the default value. 161 (merge 393050c jc/maint-fbsd-sh-ifs-workaround later to maint). 162 163 * Some scripted programs written in Python did not get updated when 164 PYTHON_PATH changed. 165 (cherry-pick 96a4647fca54031974cd6ad1 later to maint). 166 167 * When autoconf is used, any build on a different commit always ran 168 "config.status --recheck" even when unnecessary. 169 (merge 1226504 jn/less-reconfigure later to maint). 170 171 * We have been carrying a translated and long-unmaintained copy of an 172 old version of the tutorial; removed. 173 (merge 0a85441 ta/remove-stale-translated-tut later to maint). 174 175 * t4014, t9502 and t0200 tests had various portability issues that 176 broke on OpenBSD. 177 (merge 27f6342 jc/maint-test-portability later to maint). 178 179 * t9020 and t3600 tests had various portability issues. 180 (merge 5a02966 jc/test-portability later to maint). 181 182 * t9200 runs "cvs init" on a directory that already exists, but a 183 platform can configure this fail for the current user (e.g. you 184 need to be in the cvsadmin group on NetBSD 6.0). 185 (merge 8666df0 jc/test-cvs-no-init-in-existing-dir later to maint). 186 187 * t9020 and t9810 had a few non-portable shell script construct. 188 (merge 2797914 tb/test-t9020-no-which later to maint). 189 (merge 6f4e505 tb/test-t9810-no-sed-i later to maint).