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"git branch --set-upstream" is deprecated and may be removed in a 19relatively distant future. "git branch [-u|--set-upstream-to]" has 20been introduced with a saner order of arguments. 21 22 23Updates since v1.7.12 24--------------------- 25 26UI, Workflows & Features 27 28 * A credential helper for Win32 to allow access to the keychain of 29 the logged-in user has been added. 30 31 * An initial port to HP NonStop. 32 33 * A credential helper to allow access to the Gnome keyring has been 34 added. 35 36 * When "git am" sanitizes the Subject: line, we strip the prefix from 37 "Re: subject" and also from a less common "re: subject", but left 38 even less common "RE: subject" intact. 39 40 * It was tempting to say "git branch --set-upstream origin/master", 41 but that tells Git to arrange the local branch "origin/master" to 42 integrate with the currently checked out branch, which is highly 43 unlikely what the user meant. The option is deprecated; use the 44 new "--set-upstream-to" (with a short-and-sweet "-u") option 45 instead. 46 47 * "git cherry-pick" learned the "--allow-empty-message" option to 48 allow it to replay a commit without any log message. 49 50 * After "git cherry-pick -s" gave control back to the user asking 51 help to resolve conflicts, concluding "git commit" used to need to 52 be run with "-s" if the user wants to sign it off; now the command 53 leaves the sign-off line in the log template. 54 55 * "git daemon" learned the "--access-hook" option to allow an 56 external command to decline service based on the client address, 57 repository path, etc. 58 59 * "git difftool --dir-diff" learned to use symbolic links to prepare 60 temporary copy of the working tree when available. 61 62 * "git grep" learned to use a non-standard pattern type by default if 63 a configuration variable tells it to. 64 65 * "git merge-base" learned "--is-ancestor A B" option to tell if A is 66 an ancestor of B. The result is indicated by its exit status code. 67 68 * The "-Xours" backend option to "git merge -s recursive" now takes 69 effect even on binary files. 70 71 72Foreign Interface 73 74 * "git svn" has been updated to work with SVN 1.7. 75 76 * "git p4" learned "--conflicts" option to specify what to do when 77 encountering a conflict during "p4 submit". 78 79 80Performance, Internal Implementation, etc. (please report possible regressions) 81 82 * Git ships with a fall-back regexp implementation for platforms with 83 buggy regexp library, but it was easy for people to keep using their 84 platform regexp. A new test has been added to check this. 85 86 * The "check-docs" build target has been updated and greatly 87 simplified. 88 89 * The test suite is run under MALLOC_CHECK_ when running with glibc 90 that supports the feature. 91 92 * The documentation in the TeXinfo format was using indented output 93 for materials meant to be examples that are better typeset in 94 monospace. 95 96 * Compatibility wrapper around some mkdir(2) implementations that 97 reject parameter with trailing slash has been introduced. 98 99 * Compatibility wrapper for systems that lack usable setitimer() has 100 been added. 101 102 * The option parsing of "git checkout" had error checking, dwim and 103 defaulting missing options, all mixed in the code, and issuing an 104 appropriate error message with useful context was getting harder. 105 The code has been reorganized to allow giving a proper diagnosis 106 when the user says "git checkout -b -t foo bar" (e.g. "-t" is not a 107 good name for a branch). 108 109 * Many internal uses of "git merge-base" equivalent were only to see 110 if one commit fast-forwards to the other, which did not need the 111 full set of merge bases to be computed. They have been updated to 112 use less expensive checks. 113 114 * The heuristics to detect and silently convert latin1 to utf8 when 115 we were told to use utf-8 in the log message has been transplanted 116 from "mailinfo" to "commit" and "commit-tree". 117 118 * Messages given by "git <subcommand> -h" from many subcommands have 119 been marked for translation. 120 121 122Also contains minor documentation updates and code clean-ups. 123 124 125Fixes since v1.7.12 126------------------- 127 128Unless otherwise noted, all the fixes since v1.7.12 in the 129maintenance track are contained in this release (see release notes 130to them for details). 131 132 * When "git am" is fed an input that has multiple "Content-type: ..." 133 header, it did not grok charset= attribute correctly. 134 (merge 176943b jc/maint-mailinfo-mime-attr later to maint). 135 136 * "git blame MAKEFILE" run in a history that has "Makefile" but not 137 "MAKEFILE" should say "No such file MAKEFILE in HEAD", but got 138 confused on a case insensitive filesystem and failed to do so. 139 (merge 9aeaab6 jc/maint-blame-no-such-path later to maint). 140 141 * Even during a conflicted merge, "git blame $path" always meant to 142 blame uncommitted changes to the "working tree" version; make it 143 more useful by showing cleanly merged parts as coming from the other 144 branch that is being merged. 145 (merge 9aeaab6 jc/maint-blame-no-such-path later to maint). 146 147 * Documentation talked about "first line of commit log" when it meant 148 the title of the commit. The description was clarified by defining 149 how the title is decided and rewording the casual mention of "first 150 line" to "title". 151 (merge 52ffe99 jw/doc-commit-title later to maint). 152 153 * The attribute system may be asked for a path that itself or its 154 leading directories no longer exists in the working tree, and it is 155 fine if we cannot open .gitattribute file in such a case. Failure 156 to open per-directory .gitattributes with error status other than 157 ENOENT and ENOTDIR should be diagnosed, but it wasn't. 158 159 * "git log --all-match --grep=A --grep=B" ought to show commits that 160 mention both A and B, but when these three options are used with 161 --author or --committer, it showed commits that mention either A or 162 B (or both) instead. 163 (merge 39f2e01 jc/maint-log-grep-all-match later to maint). 164 165 * Earlier we made the diffstat summary line that shows the number of 166 lines added/deleted localizable, but it was found irritating having 167 to see them in various languages on a list whose discussion language 168 is English. 169 (merge 218adaa nd/maint-diffstat-summary later to maint). 170 171 * "git fetch --all", when passed "--no-tags", did not honor the 172 "--no-tags" option while fetching from individual remotes (the same 173 issue existed with "--tags", but combination "--all --tags" makes 174 much less sense than "--all --no-tags"). 175 (merge 8556646 dj/fetch-all-tags later to maint). 176 177 * The subcommand in "git remote" to remove a defined remote was 178 "rm" and the command did not take a fully-spelled "remove". 179 (merge e17dba8 nd/maint-remote-remove later to maint). 180 181 * After "gitk" showed the contents of a tag, neither "Reread 182 references" nor "Reload" did not update what is shown as the 183 contents of it, when the user overwrote the tag with "git tag -f". 184 185 * "git cvsimport" did not thoroughly cleanse tag names that it 186 inferred from the names of the tags it obtained from CVS, which 187 caused "git tag" to barf and stop the import in the middle. 188 189 * "git show --format='%ci'" did not give timestamp correctly for 190 commits created without human readable name on "committer" line. 191 (merge e27ddb6 jc/maint-ident-missing-human-name later to maint). 192 193 * "git cherry-pick A C B" used to replay changes in A and then B and 194 then C if these three commits had committer timestamps in that 195 order, which is not what the user who said "A C B" naturally 196 expects. 197 (merge a73e22e mz/cherry-pick-cmdline-order later to maint). 198 199 * "git show --quiet" ought to be a synonym for "git show -s", but 200 wasn't. 201 (merge f9c75d8 jk/maint-quiet-is-synonym-to-s-in-log later to maint). 202 203 * "git p4", when "--use-client-spec" and "--detect-branches" are used 204 together, misdetected branches. 205 (merge 21ef5df pw/p4-use-client-spec-branch-detection later to maint). 206 207 * Output from "git branch -v" contains "(no branch)" that could be 208 localized, but the code to align it along with the names of 209 branches were counting in bytes, not in display columns. 210 (merge 1452bd6 nd/branch-v-alignment later to maint). 211 212 * When looking for $HOME/.gitconfig etc., it is OK if we cannot read 213 them because they do not exist, but we did not diagnose existing 214 files that we cannot read. 215 216 * The interactive prompt "git send-email" gives was error prone. It 217 asked "What e-mail address do you want to use?" with the address it 218 guessed (correctly) the user would want to use in its prompt, 219 tempting the user to say "y". But the response was taken as "No, 220 please use 'y' as the e-mail address instead", which is most 221 certainly not what the user meant. 222 (merge 6183749 sb/send-email-reconfirm-fix later to maint).