|
| 1 | +Git v1.8.1 Release Notes |
| 2 | +======================== |
| 3 | + |
| 4 | +Backward compatibility notes |
| 5 | +---------------------------- |
| 6 | + |
| 7 | +In the next major release (not *this* one), we will change the |
| 8 | +behavior of the "git push" command. |
| 9 | + |
| 10 | +When "git push [$there]" does not say what to push, we have used the |
| 11 | +traditional "matching" semantics so far (all your branches were sent |
| 12 | +to the remote as long as there already are branches of the same name |
| 13 | +over there). We will use the "simple" semantics that pushes the |
| 14 | +current branch to the branch with the same name, only when the current |
| 15 | +branch is set to integrate with that remote branch. There is a user |
| 16 | +preference configuration variable "push.default" to change this, and |
| 17 | +"git push" will warn about the upcoming change until you set this |
| 18 | +variable in this release. |
| 19 | + |
| 20 | +"git branch --set-upstream" is deprecated and may be removed in a |
| 21 | +relatively distant future. "git branch [-u|--set-upstream-to]" has |
| 22 | +been introduced with a saner order of arguments. |
| 23 | + |
| 24 | + |
| 25 | +Updates since v1.8.0 |
| 26 | +-------------------- |
| 27 | + |
| 28 | +UI, Workflows & Features |
| 29 | + |
| 30 | + * We used to have a workaround for a bug in ancient "less" that |
| 31 | + causes it to exit without any output when the terminal is resized. |
| 32 | + The bug has been fixed in "less" version 406 (June 2007), and the |
| 33 | + workaround has been removed in this release. |
| 34 | + |
| 35 | + * A new configuration variable "diff.context" can be used to |
| 36 | + give the default number of context lines in the patch output, to |
| 37 | + override the hardcoded default of 3 lines. |
| 38 | + |
| 39 | + * "git format-patch" leraned the "--notes=<ref>" option to give |
| 40 | + notes for the commit after the three-dash lines in its output. |
| 41 | + |
| 42 | + * "git log --grep=<pcre>" learned to honor the "grep.patterntype" |
| 43 | + configuration set to "perl". |
| 44 | + |
| 45 | + * "git rm $submodule" used to punt on removing a submodule working |
| 46 | + tree to avoid losing the repository embedded in it. Because |
| 47 | + recent git uses a mechanism to separate the submodule repository |
| 48 | + from the submodule working tree, "git rm" learned to detect this |
| 49 | + case and removes the submodule working tree when it is safe. |
| 50 | + |
| 51 | + * "git submodule add" learned to add a new submodule at the same |
| 52 | + path as the path where an unrelated submodule was bound to in an |
| 53 | + existing revision via the "--name" option. |
| 54 | + |
| 55 | + * "git submodule sync" learned the "--recursive" option. |
| 56 | + |
| 57 | + * "git symbolic-ref" learned the "-d $symref" option to delete the |
| 58 | + named symbolic ref, which is more intuitive way to spell it than |
| 59 | + "update-ref -d --no-deref". |
| 60 | + |
| 61 | + |
| 62 | +Foreign Interface |
| 63 | + |
| 64 | + * "git cvsimport" can be told to record timezones (other than GMT) |
| 65 | + per-author via its author info file. |
| 66 | + |
| 67 | + * The remote helper interface to interact with subversion |
| 68 | + repositories (one of the GSoC 2012 projects) has been merged. |
| 69 | + |
| 70 | + |
| 71 | +Performance, Internal Implementation, etc. |
| 72 | + |
| 73 | + * The logic to generate the initial advertisement from |
| 74 | + "upload-pack" (what is invoked by "git fetch" on the other side |
| 75 | + of the connection) to list what refs are available in the |
| 76 | + repository has been optimized. |
| 77 | + |
| 78 | + * The logic to find set of attributes that match a given path has |
| 79 | + been optimized. |
| 80 | + |
| 81 | + |
| 82 | +Also contains minor documentation updates and code clean-ups. |
| 83 | + |
| 84 | + |
| 85 | +Fixes since v1.8.0 |
| 86 | +------------------ |
| 87 | + |
| 88 | +Unless otherwise noted, all the fixes since v1.8.0 in the maintenance |
| 89 | +track are contained in this release (see release notes to them for |
| 90 | +details). |
| 91 | + |
| 92 | + * The configuration parser had an unnecessary hardcoded limit on |
| 93 | + variable names that was not checked consistently. |
| 94 | + (merge 0971e99 bw/config-lift-variable-name-length-limit later to maint). |
| 95 | + |
| 96 | + * The "say" function in the test scaffolding incorrectly allowed |
| 97 | + "echo" to interpret "\a" as if it were a C-string asking for a |
| 98 | + BEL output. |
| 99 | + (merge 7bc0911 jc/test-say-color-avoid-echo-escape later to maint). |
| 100 | + |
| 101 | + * "git mergetool" feeds /dev/null as a common ancestor when dealing |
| 102 | + with an add/add conflict, but p4merge backend cannot handle |
| 103 | + it. Work it around by passing a temporary empty file. |
| 104 | + (merge 3facc60 da/mergetools-p4 later to maint). |
| 105 | + |
| 106 | + * "git log -F -E --grep='<ere>'" failed to use the given <ere> |
| 107 | + pattern as extended regular expression, and instead looked for the |
| 108 | + string literally. |
| 109 | + (merge 727b6fc jc/grep-pcre-loose-ends~1 later to maint). |
| 110 | + |
| 111 | + * "git grep -e pattern <tree>" asked the attribute system to read |
| 112 | + "<tree>:.gitattributes" file in the working tree, which was |
| 113 | + nonsense. |
| 114 | + (merge 55c6168 nd/grep-true-path later to maint). |
| 115 | + |
| 116 | + * A symbolic ref refs/heads/SYM was not correctly removed with "git |
| 117 | + branch -d SYM"; the command removed the ref pointed by SYM |
| 118 | + instead. |
| 119 | + (merge 13baa9f rs/branch-del-symref later to maint). |
| 120 | + |
| 121 | + * Update "remote tracking branch" in the documentation to |
| 122 | + "remote-tracking branch". |
| 123 | + (merge a6d3bde mm/maint-doc-remote-tracking later to maint). |
| 124 | + |
| 125 | + * "git pull --rebase" run while the HEAD is detached tried to find |
| 126 | + the upstream branch of the detached HEAD (which by definition |
| 127 | + does not exist) and emitted unnecessary error messages. |
| 128 | + (merge e980765 ph/pull-rebase-detached later to maint). |
| 129 | + |
| 130 | + * The refs/replace hierarchy was not mentioned in the |
| 131 | + repository-layout docs. |
| 132 | + (merge 11fbe18 po/maint-refs-replace-docs later to maint). |
| 133 | + |
| 134 | + * Various rfc2047 quoting issues around a non-ASCII name on the |
| 135 | + From: line in the output from format-patch has been corrected. |
| 136 | + (merge 25dc8da js/format-2047 later to maint). |
| 137 | + |
| 138 | + * Sometimes curl_multi_timeout() function suggested a wrong timeout |
| 139 | + value when there is no file descriptors to wait on and the http |
| 140 | + transport ended up sleeping for minutes in select(2) system call. |
| 141 | + A workaround has been added for this. |
| 142 | + (merge 7202b81 sz/maint-curl-multi-timeout later to maint). |
| 143 | + |
| 144 | + * For a fetch refspec (or the result of applying wildcard on one), |
| 145 | + we always want the RHS to map to something inside "refs/" |
| 146 | + hierarchy, but the logic to check it was not exactly right. |
| 147 | + (merge 5c08c1f jc/maint-fetch-tighten-refname-check later to maint). |
| 148 | + |
| 149 | + * "git diff -G<pattern>" did not honor textconv filter when looking |
| 150 | + for changes. |
| 151 | + (merge b1c2f57 jk/maint-diff-grep-textconv later to maint). |
0 commit comments