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