1Git v1.8.3 Release Notes 2======================== 3 4Backward compatibility notes (for Git 2.0) 5------------------------------------------ 6 7When "git push [$there]" does not say what to push, we have used the 8traditional "matching" semantics so far (all your branches were sent 9to the remote as long as there already are branches of the same name 10over there). In Git 2.0, the default will change to the "simple" 11semantics that pushes the current branch to the branch with the same 12name, only when the current branch is set to integrate with that 13remote branch. There is a user preference configuration variable 14"push.default" to change this. If you are an old-timer who is used 15to the "matching" semantics, you can set it to "matching" to keep the 16traditional behaviour. If you want to live in the future early, 17you can set it to "simple" today without waiting for Git 2.0. 18 19When "git add -u" and "git add -A", that does not specify what paths 20to add on the command line is run from inside a subdirectory, these 21commands will operate on the entire tree in Git 2.0 for consistency 22with "git commit -a" and other commands. Because there will be no 23mechanism to make "git add -u" behave as if "git add -u .", it is 24important for those who are used to "git add -u" (without pathspec) 25updating the index only for paths in the current subdirectory to start 26training their fingers to explicitly say "git add -u ." when they mean 27it before Git 2.0 comes. 28 29 30Updates since v1.8.2 31-------------------- 32 33UI, Workflows & Features 34 35 * When the interactive access to git-shell is not enabled, it issues 36 a message meant to help the system admininstrator to enable it. 37 An explicit way to help the end users who connect to the service by 38 issuing custom messages to refuse such an access has been added. 39 40 * "git status" suggests users to look into using--untracked=no option 41 when it takes too long. 42 43 * "git fetch" learned to fetch a commit at the tip of an unadvertised 44 ref by specifying a raw object name from the command line when the 45 server side supports this feature. 46 47 * "git count-objects -v" learned to report leftover temporary 48 packfiles and other garbage in the object store. 49 50 * A new read-only credential helper (in contrib/) to interact with 51 the .netrc/.authinfo files has been added. 52 53 * "git send-email" can be used with the credential helper system. 54 55 * There was no Porcelain way to say "I no longer am interested in 56 this submodule", once you express your interest in a submodule with 57 "submodule init". "submodule deinit" is the way to do so. 58 59 * "git pull --rebase" learned to pass "-v/-q" options to underlying 60 "git rebase". 61 62 * The new "--follow-tags" option tells "git push" to push relevant 63 annotated tags when pushing branches out. 64 65 * "git mergetool" now feeds files to the "p4merge" backend in the 66 order that matches the p4 convention, where "theirs" is usually 67 shown on the left side, which is the opposite from other backend 68 expects. 69 70 71Performance, Internal Implementation, etc. 72 73 * Updates for building under msvc. 74 75 * A few codepaths knew how much data they need to put in the 76 hashtables they use upfront, but still started from a small table 77 repeatedly growing and rehashing. 78 79 * The API to walk reflog entries from the latest to older, which was 80 necessary for operations such as "git checkout -", was cumbersome 81 to use correctly and also inefficient. 82 83 84Also contains minor documentation updates and code clean-ups. 85 86 87Fixes since v1.8.2 88------------------ 89 90Unless otherwise noted, all the fixes since v1.8.2 in the maintenance 91track are contained in this release (see release notes to them for 92details). 93 94 * Annotated tags outside refs/tags/ hierarchy were not advertised 95 correctly to the ls-remote and fetch with recent version of Git. 96 (merge c29c46f jk/fully-peeled-packed-ref later to maint). 97 98 * Recent optimization broke shallow clones. 99 (merge f59de5d jk/peel-ref later to maint). 100 101 * "git cmd -- ':(top'" was not diagnosed as an invalid syntax, and 102 instead the parser kept reading beyond the end of the string. 103 (merge f612a67 lf/setup-prefix-pathspec later to maint). 104 105 * "git tag -f <tag>" always said "Updated tag '<tag>'" even when 106 creating a new tag (i.e. not overwriting nor updating). 107 (merge 3ae851e ph/tag-force-no-warn-on-creation later to maint). 108 109 * "git p4" did not behave well when the path to the root of the P4 110 client was not its real path. 111 (merge bbd8486 pw/p4-symlinked-root later to maint). 112 113 * "git archive" reports a failure when asked to create an archive out 114 of an empty tree. It would be more intuitive to give an empty 115 archive back in such a case. 116 (merge bd54cf1 jk/empty-archive later to maint). 117 118 * When "format-patch" quoted a non-ascii strings on the header files, 119 it incorrectly applied rfc2047 and chopped a single character in 120 the middle of it. 121 (merge 6cd3c05 ks/rfc2047-one-char-at-a-time later to maint). 122 123 * An aliased command spawned from a bare repository that does not say 124 it is bare with "core.bare = yes" is treated as non-bare by mistake. 125 (merge 2cd83d1 jk/alias-in-bare later to maint). 126 127 * In "git reflog expire", REACHABLE bit was not cleared from the 128 correct objects. 129 130 * The logic used by "git diff -M --stat" to shorten the names of 131 files before and after a rename did not work correctly when the 132 common prefix and suffix between the two filenames overlapped. 133 (merge b174eb4 ap/maint-diff-rename-avoid-overlap later to maint). 134 135 * The "--match=<pattern>" option of "git describe", when used with 136 "--all" to allow refs that are not annotated tags to be used as a 137 base of description, did not restrict the output from the command 138 to those that match the given pattern. 139 (merge 46e1d6e jc/describe later to maint). 140 141 * Clarify in the documentation "what" gets pushed to "where" when the 142 command line to "git push" does not say these explicitly. 143 144 * The "--color=<when>" argument to the commands in the diff family 145 was described poorly. 146 147 * The arguments given to pre-rebase hook were not documented. 148 149 * The v4 index format was not documented. 150 151 * The "--match=<pattern>" argument "git describe" takes uses glob 152 pattern but it wasn't obvious from the documentation. 153 154 * Some sources failed to compile on systems that lack NI_MAXHOST in 155 their system header (e.g. z/OS). 156 157 * Add an example use of "--env-filter" in "filter-branch" 158 documentation. 159 160 * "git bundle verify" did not say "records a complete history" for a 161 bundle that does not have any prerequisites. 162 163 * In the v1.8.0 era, we changed symbols that do not have to be global 164 to file scope static, but a few functions in graph.c were used by 165 CGit from sideways bypassing the entry points of the API the 166 in-tree users use. 167 168 * "git update-index -h" did not do the usual "-h(elp)" thing. 169 170 * "git index-pack" had a buffer-overflow while preparing an 171 informational message when the translated version of it was too 172 long. 173 174 * 'git commit -m "$msg"' used to add an extra newline even when 175 $msg already ended with one. 176 (merge 46fbf75 bc/commit-complete-lines-given-via-m-option later to maint). 177 178 * The SSL peer verification done by "git imap-send" did not ask for 179 Server Name Indication (RFC 4366), failing to connect SSL/TLS 180 sites that serve multiple hostnames on a single IP. 181 182 * perl/Git.pm::cat_blob slurped everything in core only to write it 183 out to a file descriptor, which was not a very smart thing to do. 184 185 * "git branch" did not bother to check nonsense command line 186 parameters and issue errors in many cases. 187 188 * Verification of signed tags were not done correctly when not in C 189 or en/US locale. 190 (merge 0174eea mg/gpg-interface-using-status later to maint). 191 192 * Some platforms and users spell UTF-8 differently; retry with the 193 most official "UTF-8" when the system does not understand the 194 user-supplied encoding name that are the common alternative 195 spellings of UTF-8. 196 197 * When export-subst is used, "zip" output recorded incorrect 198 size of the file. 199 200 * "git am $maildir/" applied messages in an unexpected order; sort 201 filenames read from the maildir/ in a way that is more likely to 202 sort messages in the order the writing MUA meant to, by sorting 203 numeric segment in numeric order and non-numeric segment in 204 alphabetical order. 205 206 * "git submodule update", when recursed into sub-submodules, did not 207 acccumulate the prefix paths.