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 62 63Performance, Internal Implementation, etc. (please report possible regressions) 64 65 * Git ships with a fall-back regexp implementation for platforms with 66 buggy regexp library, but it was easy for people to keep using their 67 platform regexp. A new test has been added to check this. 68 69 * The "check-docs" build target has been updated and greatly 70 simplified. 71 72 * The documentation in the TeXinfo format was using indented output 73 for materials meant to be examples that are better typeset in 74 monospace. 75 76 * Compatibility wrapper around some mkdir(2) implementations that 77 reject parameter with trailing slash has been introduced. 78 79 * Compatibility wrapper for systems that lack usable setitimer() has 80 been added. 81 82 * Many internal uses of "git merge-base" equivalent were only to see 83 if one commit fast-forwards to the other, which did not need the 84 full set of merge bases to be computed. They have been updated to 85 use less expensive checks. 86 87 * The heuristics to detect and silently convert latin1 to utf8 when 88 we were told to use utf-8 in the log message has been transplanted 89 from "mailinfo" to "commit" and "commit-tree". 90 91 * Messages given by "git <subcommand> -h" from many subcommands have 92 been marked for translation. 93 94 95Also contains minor documentation updates and code clean-ups. 96 97 98Fixes since v1.7.12 99------------------- 100 101Unless otherwise noted, all the fixes since v1.7.12 in the 102maintenance track are contained in this release (see release notes 103to them for details). 104 105 * The subcommand in "git remote" to remove a defined remote was 106 "rm" and the command did not take a fully-spelled "remove". 107 (merge e17dba8 nd/maint-remote-remove later to maint). 108 109 * After "gitk" showed the contents of a tag, neither "Reread 110 references" nor "Reload" did not update what is shown as the 111 contents of it, when the user overwrote the tag with "git tag -f". 112 113 * "git cvsimport" did not thoroughly cleanse tag names that it 114 inferred from the names of the tags it obtained from CVS, which 115 caused "git tag" to barf and stop the import in the middle. 116 117 * "git show --format='%ci'" did not give timestamp correctly for 118 commits created without human readable name on "committer" line. 119 (merge e27ddb6 jc/maint-ident-missing-human-name later to maint). 120 121 * "git cherry-pick A C B" used to replay changes in A and then B and 122 then C if these three commits had committer timestamps in that 123 order, which is not what the user who said "A C B" naturally 124 expects. 125 (merge a73e22e mz/cherry-pick-cmdline-order later to maint). 126 127 * "git show --quiet" ought to be a synonym for "git show -s", but 128 wasn't. 129 (merge f9c75d8 jk/maint-quiet-is-synonym-to-s-in-log later to maint). 130 131 * "git p4", when "--use-client-spec" and "--detect-branches" are used 132 together, misdetected branches. 133 (merge 21ef5df pw/p4-use-client-spec-branch-detection later to maint). 134 135 * Output from "git branch -v" contains "(no branch)" that could be 136 localized, but the code to align it along with the names of 137 branches were counting in bytes, not in display columns. 138 (merge 1452bd6 nd/branch-v-alignment later to maint). 139 140 * When looking for $HOME/.gitconfig etc., it is OK if we cannot read 141 them because they do not exist, but we did not diagnose existing 142 files that we cannot read. 143 144 * The interactive prompt "git send-email" gives was error prone. It 145 asked "What e-mail address do you want to use?" with the address it 146 guessed (correctly) the user would want to use in its prompt, 147 tempting the user to say "y". But the response was taken as "No, 148 please use 'y' as the e-mail address instead", which is most 149 certainly not what the user meant. 150 (merge 6183749 sb/send-email-reconfirm-fix later to maint).