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 * It was tempting to say "git branch --set-upstream origin/master", 35 but that tells Git to arrange the local branch "origin/master" to 36 integrate with the currently checked out branch, which is highly 37 unlikely what the user meant. The option is deprecated; use the 38 new "--set-upstream-to" (with a short-and-sweet "-u") option 39 instead. 40 41 * "git cherry-pick" learned the "--allow-empty-message" option to 42 allow it to replay a commit without any log message. 43 44 * "git daemon" learned the "--access-hook" option to allow an 45 external command to decline service based on the client address, 46 repository path, etc. 47 48 * "git difftool --dir-diff" learned to use symbolic links to prepare 49 temporary copy of the working tree when available. 50 51 * "git grep" learned to use a non-standard pattern type by default if 52 a configuration variable tells it to. 53 54 * "git merge-base" learned "--is-ancestor A B" option to tell if A is 55 an ancestor of B. The result is indicated by its exit status code. 56 57 58Foreign Interface 59 60 * "git svn" has been updated to work with SVN 1.7. 61 62Performance, Internal Implementation, etc. (please report possible regressions) 63 64 * Git ships with a fall-back regexp implementation for platforms with 65 buggy regexp library, but it was easy for people to keep using their 66 platform regexp. A new test has been added to check this. 67 68 * The "check-docs" build target has been updated and greatly 69 simplified. 70 71 * The documentation in the TeXinfo format was using indented output 72 for materials meant to be examples that are better typeset in 73 monospace. 74 75 * Compatibility wrapper around some mkdir(2) implementations that 76 reject parameter with trailing slash has been introduced. 77 78 * Many internal uses of "git merge-base" equivalent were only to see 79 if one commit fast-forwards to the other, which did not need the 80 full set of merge bases to be computed. They have been updated to 81 use less expensive checks. 82 83 * The heuristics to detect and silently convert latin1 to utf8 when 84 we were told to use utf-8 in the log message has been transplanted 85 from "mailinfo" to "commit" and "commit-tree". 86 87 * Messages given by "git <subcommand> -h" from many subcommands have 88 been marked for translation. 89 90Also contains minor documentation updates and code clean-ups. 91 92 93Fixes since v1.7.12 94------------------- 95 96Unless otherwise noted, all the fixes since v1.7.12 in the 97maintenance track are contained in this release (see release notes 98to them for details). 99 100 * "git show --format='%ci'" did not give timestamp correctly for 101 commits created without human readable name on "committer" line. 102 (merge e27ddb6 jc/maint-ident-missing-human-name later to maint). 103 104 * "git cherry-pick A C B" used to replay changes in A and then B and 105 then C if these three commits had committer timestamps in that 106 order, which is not what the user who said "A C B" naturally 107 expects. 108 (merge a73e22e mz/cherry-pick-cmdline-order later to maint). 109 110 * "git show --quiet" ought to be a synonym for "git show -s", but 111 wasn't. 112 (merge f9c75d8 jk/maint-quiet-is-synonym-to-s-in-log later to maint). 113 114 * "git p4", when "--use-client-spec" and "--detect-branches" are used 115 together, misdetected branches. 116 (merge 21ef5df pw/p4-use-client-spec-branch-detection later to maint). 117 118 * Output from "git branch -v" contains "(no branch)" that could be 119 localized, but the code to align it along with the names of 120 branches were counting in bytes, not in display columns. 121 (merge 1452bd6 nd/branch-v-alignment later to maint). 122 123 * "git for-each-ref" did not currectly support more than one --sort 124 option. 125 (merge 3b51222 kk/maint-for-each-ref-multi-sort later to maint). 126 127 * Pushing to smart HTTP server with recent Git fails without having 128 the username in the URL to force authentication, if the server is 129 configured to allow GET anonymously, while requiring authentication 130 for POST. 131 (merge b81401c jk/maint-http-half-auth-push later to maint). 132 133 * When looking for $HOME/.gitconfig etc., it is OK if we cannot read 134 them because they do not exist, but we did not diagnose existing 135 files that we cannot read. 136 137 * The synopsis said "checkout [-B branch]" to make it clear the 138 branch name is a parameter to the option, but the heading for the 139 option description was "-B::", not "-B branch::", making the 140 documentation misleading. There may be room in documentation pages 141 of other commands for similar improvements (hint, hint). 142 (merge 45aaf03 jc/maint-doc-checkout-b-always-takes-branch-name later to maint). 143 144 * "git log .." errored out saying it is both rev range and a path 145 when there is no disambiguating "--" is on the command line. 146 Update the command line parser to interpret ".." as a path in such 147 a case. 148 (merge 003c84f jc/dotdot-is-parent-directory later to maint). 149 150 * "git apply -p0" did not parse pathnames on "diff --git" line 151 correctly. This caused patches that had pathnames in no other 152 places to be mistakenly rejected (most notably, binary patch that 153 does not rename nor change mode). Textual patches, renames or mode 154 changes have preimage and postimage pathnames in different places 155 in a form that can be parsed unambiguously and did not suffer from 156 this problem. 157 (merge 6a2abdc jc/apply-binary-p0 later to maint). 158 159 * The interactive prompt "git send-email" gives was error prone. It 160 asked "What e-mail address do you want to use?" with the address it 161 guessed (correctly) the user would want to use in its prompt, 162 tempting the user to say "y". But the response was taken as "No, 163 please use 'y' as the e-mail address instead", which is most 164 certainly not what the user meant. 165 (merge 51bbccf jc/send-email-reconfirm later to maint).