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 blame" (and "git diff") learned the "--no-follow" option. 45 46 * "git cherry-pick" can be used to replay a root commit to an unborn 47 branch. 48 49 * "git commit" can be told to use --cleanup=whitespace by setting the 50 configuration variable commit.cleanup to 'whitespace'. 51 52 * "git fetch --mirror" and fetch that uses other forms of refspec 53 with wildcard used to attempt to update a symbolic ref that match 54 the wildcard on the receiving end, which made little sense (the 55 real ref that is pointed at by the symbolic ref would be updated 56 anyway). Symbolic refs no longer are affected by such a fetch. 57 58 * "git format-patch" now detects more cases in which a whole branch 59 is being exported, and uses the description for the branch, when 60 asked to write a cover letter for the series. 61 62 * "git format-patch" learned "-v $count" option, and prepends a 63 string "v$count-" to the names of its output files, and also 64 automatically sets the subject prefix to "PATCH v$count". This 65 allows patches from rerolled series to be stored under different 66 names and makes it easier to reuse cover letter messsages. 67 68 * "git log" and friends can be told with --use-mailmap option to 69 rewrite the names and email addresses of people using the mailmap 70 mechanism. 71 72 * "git push" now requires "-f" to update a tag, even if it is a 73 fast-forward, as tags are meant to be fixed points. 74 75 * When "git rebase" fails to generate patches to be applied (e.g. due 76 to oom), it failed to detect the failure and instead behaved as if 77 there were nothing to do. A workaround to use a temporary file has 78 been applied, but we probably would want to revisit this later, as 79 it hurts the common case of not failing at all. 80 81 * "git submodule" started learning a new mode to integrate with the 82 tip of the remote branch (as opposed to integrating with the commit 83 recorded in the superproject's gitlink). 84 85 86Foreign Interface 87 88 * "git fast-export" has been updated for its use in the context of 89 the remote helper interface. 90 91 * A new remote helper to interact with bzr has been added to contrib/. 92 93 94Performance, Internal Implementation, etc. 95 96 * "git fsck" has been taught to be pickier about entries in tree 97 objects that should not be there, e.g. ".", ".git", and "..". 98 99 * Matching paths with common forms of pathspecs that contain wildcard 100 characters has been optimized further. 101 102 * The implementation of "imap-send" has been updated to reuse xml 103 quoting code from http-push codepath. 104 105 * There is a simple-minded checker for the test scripts in t/ 106 directory to catch most common mistakes (it is not enabled by 107 default). 108 109 110Also contains minor documentation updates and code clean-ups. 111 112 113Fixes since v1.8.1 114------------------ 115 116Unless otherwise noted, all the fixes since v1.8.1 in the maintenance 117track are contained in this release (see release notes to them for 118details). 119 120 * An element on GIT_CEILING_DIRECTORIES list that does not name the 121 real path to a directory (i.e. a symbolic link) could have caused 122 the GIT_DIR discovery logic to escape the ceiling. 123 (merge 059b379 mh/ceiling later to maint). 124 125 * When attempting to read the XDG-style $HOME/.config/git/config and 126 finding that $HOME/.config/git is a file, we gave a wrong error 127 message, instead of treating the case as "a custom config file does 128 not exist there" and moving on. 129 (merge 8f2bbe4 jn/warn-on-inaccessible-loosen later to maint). 130 131 * The behaviour visible to the end users was confusing, when they 132 attempt to kill a process spawned in the editor that was in turn 133 launched by Git with SIGINT (or SIGQUIT), as Git would catch that 134 signal and die. We ignore these signals now. 135 (merge 1250857 pf/editor-ignore-sigint later to maint). 136 137 * A child process that was killed by a signal (e.g. SIGINT) was 138 reported in an inconsistent way depending on how the process was 139 spawned by us, with or without a shell in between. 140 (merge 709ca73 jk/unify-exit-code-by-receiving-signal later to maint). 141 142 * After failing to create a temporary file using mkstemp(), failing 143 pathname was not reported correctly on some platforms. 144 (merge f7be59b jc/mkstemp-more-careful-error-reporting later to maint). 145 146 * The attribute mechanism didn't allow limiting attributes to be 147 applied to only a single directory itself with "path/" like the 148 exclude mechanism does. 149 (merge 94bc671 ja/directory-attrs later to maint). 150 151 * "git apply" misbehaved when fixing whitespace breakages by removing 152 excess trailing blank lines. 153 (merge 5de7166 jc/apply-trailing-blank-removal later to maint). 154 155 * A tar archive created by "git archive" recorded a directory in a 156 way that made NetBSD's implementation of "tar" sometimes unhappy. 157 (merge 22f0dcd rs/leave-base-name-in-name-field-of-tar later to maint). 158 159 * "git archive" did not record uncompressed size in the header when 160 streaming a zip archive, which confused some implementations of unzip. 161 (merge 5ea2c84 rs/zip-with-uncompressed-size-in-the-header later to maint). 162 163 * When "git clone --separate-git-dir=$over_there" is interrupted, it 164 failed to remove the real location of the $GIT_DIR it created. 165 This was most visible when interrupting a submodule update. 166 (merge 9be1980 jl/interrupt-clone-remove-separate-git-dir later to maint). 167 168 * The way "git svn" asked for password using SSH_ASKPASS and 169 GIT_ASKPASS was not in line with the rest of the system. 170 (merge e9263e4 ss/svn-prompt later to maint). 171 172 * The --graph code fell into infinite loop when asked to do what the 173 code did not expect. 174 (merge 656197a mk/maint-graph-infinity-loop later to maint). 175 176 * http transport was wrong to ask for the username when the 177 authentication is done by certificate identity. 178 (merge 75e9a40 rb/http-cert-cred-no-username-prompt later to maint). 179 180 * "git pack-refs" that ran in parallel to another process that 181 created new refs had a nasty race. 182 (merge b3f1280 jk/repack-ref-racefix later to maint). 183 184 * After "git add -N" and then writing a tree object out of the 185 index, the cache-tree data structure got corrupted. 186 (merge eec3e7e nd/invalidate-i-t-a-cache-tree later to maint). 187 188 * "git merge --no-edit" computed who were involved in the work done 189 on the side branch, even though that information is to be discarded 190 without getting seen in the editor. 191 (merge 9bcbb1c jc/maint-fmt-merge-msg-no-edit-lose-credit later to maint). 192 193 * "git merge" started calling prepare-commit-msg hook like "git 194 commit" does some time ago, but forgot to pay attention to the exit 195 status of the hook. 196 (merge 3e4141d ap/merge-stop-at-prepare-commit-msg-failure later to maint). 197 198 * When users spell "cc:" in lowercase in the fake "header" in the 199 trailer part, "git send-email" failed to pick up the addresses from 200 there. As e-mail headers field names are case insensitive, this 201 script should follow suit and treat "cc:" and "Cc:" the same way. 202 (merge 6310071 nz/send-email-headers-are-case-insensitive later to maint). 203 204 * Output from "git status --ignored" showed an unexpected interaction 205 with "--untracked". 206 (merge a45fb69 ap/status-ignored-in-ignored-directory later to maint). 207 208 * "gitweb", when sorting by age to show repositories with new 209 activities first, used to sort repositories with absolutely 210 nothing in it early, which was not very useful. 211 (merge 28dae18 md/gitweb-sort-by-age later to maint). 212 213 * "gitweb"'s code to sanitize control characters before passing it to 214 "highlight" filter lost known-to-be-safe control characters by 215 mistake. 216 (merge 0e901d2 os/gitweb-highlight-uncaptured later to maint). 217 218 * When a line to be wrapped has a solid run of non space characters 219 whose length exactly is the wrap width, "git shortlog -w" failed 220 to add a newline after such a line. 221 (merge e0db176 sp/shortlog-missing-lf later to maint). 222 223 * Command line completion leaked an unnecessary error message while 224 looking for possible matches with paths in <tree-ish>. 225 (merge ca87dd6 ds/completion-silence-in-tree-path-probe later to maint). 226 227 * Command line completion for "tcsh" emitted an unwanted space 228 after completing a single directory name. 229 (merge 92f1c04 mk/complete-tcsh later to maint). 230 231 * Some shells do not behave correctly when IFS is unset; work it 232 around by explicitly setting it to the default value. 233 (merge 393050c jc/maint-fbsd-sh-ifs-workaround later to maint). 234 235 * Some scripted programs written in Python did not get updated when 236 PYTHON_PATH changed. 237 (cherry-pick 96a4647fca54031974cd6ad1 later to maint). 238 239 * When autoconf is used, any build on a different commit always ran 240 "config.status --recheck" even when unnecessary. 241 (merge 1226504 jn/less-reconfigure later to maint). 242 243 * We have been carrying a translated and long-unmaintained copy of an 244 old version of the tutorial; removed. 245 (merge 0a85441 ta/remove-stale-translated-tut later to maint). 246 247 * t4014, t9502 and t0200 tests had various portability issues that 248 broke on OpenBSD. 249 (merge 27f6342 jc/maint-test-portability later to maint). 250 251 * t9020 and t3600 tests had various portability issues. 252 (merge 5a02966 jc/test-portability later to maint). 253 254 * t9200 runs "cvs init" on a directory that already exists, but a 255 platform can configure this fail for the current user (e.g. you 256 need to be in the cvsadmin group on NetBSD 6.0). 257 (merge 8666df0 jc/test-cvs-no-init-in-existing-dir later to maint). 258 259 * t9020 and t9810 had a few non-portable shell script construct. 260 (merge 2797914 tb/test-t9020-no-which later to maint). 261 (merge 6f4e505 tb/test-t9810-no-sed-i later to maint).