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 * In addition to the case where the user edits the log message with 41 the "e)dit" option of "am -i", replace the "Applying: this patch" 42 message with the final log message contents after applymsg hook 43 munges it. 44 45 * "git status" suggests users to look into using --untracked=no option 46 when it takes too long. 47 48 * "git status" shows a bit more information to "git status" during a 49 rebase/bisect session. 50 51 * "git fetch" learned to fetch a commit at the tip of an unadvertised 52 ref by specifying a raw object name from the command line when the 53 server side supports this feature. 54 55 * "git count-objects -v" learned to report leftover temporary 56 packfiles and other garbage in the object store. 57 58 * A new read-only credential helper (in contrib/) to interact with 59 the .netrc/.authinfo files has been added. 60 61 * "git send-email" can be used with the credential helper system. 62 63 * There was no Porcelain way to say "I no longer am interested in 64 this submodule", once you express your interest in a submodule with 65 "submodule init". "submodule deinit" is the way to do so. 66 67 * "git pull --rebase" learned to pass "-v/-q" options to underlying 68 "git rebase". 69 70 * The new "--follow-tags" option tells "git push" to push relevant 71 annotated tags when pushing branches out. 72 73 * "git mergetool" now feeds files to the "p4merge" backend in the 74 order that matches the p4 convention, where "theirs" is usually 75 shown on the left side, which is the opposite from other backend 76 expects. 77 78 * "show/log" now honors gpg.program configuration just like other 79 parts of the code that use GnuPG. 80 81 * "git log" that shows the difference between the parent and the 82 child has been optimized somewhat. 83 84 85Performance, Internal Implementation, etc. 86 87 * Updates for building under msvc. 88 89 * A few codepaths knew how much data they need to put in the 90 hashtables they use upfront, but still started from a small table 91 repeatedly growing and rehashing. 92 93 * The API to walk reflog entries from the latest to older, which was 94 necessary for operations such as "git checkout -", was cumbersome 95 to use correctly and also inefficient. 96 97 * Codepaths that inspect log-message-to-be and decide when to add a 98 new Signed-off-by line in various commands have been consolidated. 99 100 * The pkt-line API, implementation and its callers have been cleaned 101 up to make them more robust. 102 103 * Cygwin port has a faster-but-lying lstat(2) emulation whose 104 incorrectness does not matter in practice except for a few 105 codepaths, and setting permission bits to directories is a codepath 106 that needs to use a more correct one. 107 108 109Also contains minor documentation updates and code clean-ups. 110 111 112Fixes since v1.8.2 113------------------ 114 115Unless otherwise noted, all the fixes since v1.8.2 in the maintenance 116track are contained in this release (see release notes to them for 117details). 118 119 * "index-pack --fix-thin" used uninitialize value to compute delta 120 depths of objects it appends to the resulting pack. 121 (merge 57165db jk/index-pack-correct-depth-fix later to maint). 122 123 * "index-pack --verify-stat" used a few counters outside protection 124 of mutex, possibly showing incorrect numbers. 125 (merge 8f82aad nd/index-pack-threaded-fixes later to maint). 126 127 * The code to keep track of what directory names are known to Git on 128 platforms with case insensitive filesystems can get confused upon a 129 hash collision between these pathnames and looped forever. 130 (merge 2092678 kb/name-hash later to maint). 131 132 * Annotated tags outside refs/tags/ hierarchy were not advertised 133 correctly to the ls-remote and fetch with recent version of Git. 134 (merge c29c46f jk/fully-peeled-packed-ref later to maint). 135 136 * Recent optimization broke shallow clones. 137 (merge f59de5d jk/peel-ref later to maint). 138 139 * "git cmd -- ':(top'" was not diagnosed as an invalid syntax, and 140 instead the parser kept reading beyond the end of the string. 141 (merge f612a67 lf/setup-prefix-pathspec later to maint). 142 143 * "git tag -f <tag>" always said "Updated tag '<tag>'" even when 144 creating a new tag (i.e. not overwriting nor updating). 145 (merge 3ae851e ph/tag-force-no-warn-on-creation later to maint). 146 147 * "git p4" did not behave well when the path to the root of the P4 148 client was not its real path. 149 (merge bbd8486 pw/p4-symlinked-root later to maint). 150 151 * "git archive" reports a failure when asked to create an archive out 152 of an empty tree. It would be more intuitive to give an empty 153 archive back in such a case. 154 (merge bd54cf1 jk/empty-archive later to maint). 155 156 * When "format-patch" quoted a non-ascii strings on the header files, 157 it incorrectly applied rfc2047 and chopped a single character in 158 the middle of it. 159 (merge 6cd3c05 ks/rfc2047-one-char-at-a-time later to maint). 160 161 * An aliased command spawned from a bare repository that does not say 162 it is bare with "core.bare = yes" is treated as non-bare by mistake. 163 (merge 2cd83d1 jk/alias-in-bare later to maint). 164 165 * In "git reflog expire", REACHABLE bit was not cleared from the 166 correct objects. 167 168 * The logic used by "git diff -M --stat" to shorten the names of 169 files before and after a rename did not work correctly when the 170 common prefix and suffix between the two filenames overlapped. 171 172 * The "--match=<pattern>" option of "git describe", when used with 173 "--all" to allow refs that are not annotated tags to be used as a 174 base of description, did not restrict the output from the command 175 to those that match the given pattern. 176 (merge 46e1d6e jc/describe later to maint). 177 178 * Clarify in the documentation "what" gets pushed to "where" when the 179 command line to "git push" does not say these explicitly. 180 181 * The "--color=<when>" argument to the commands in the diff family 182 was described poorly. 183 184 * The arguments given to pre-rebase hook were not documented. 185 186 * The v4 index format was not documented. 187 188 * The "--match=<pattern>" argument "git describe" takes uses glob 189 pattern but it wasn't obvious from the documentation. 190 191 * Some sources failed to compile on systems that lack NI_MAXHOST in 192 their system header (e.g. z/OS). 193 194 * Add an example use of "--env-filter" in "filter-branch" 195 documentation. 196 197 * "git bundle verify" did not say "records a complete history" for a 198 bundle that does not have any prerequisites. 199 200 * In the v1.8.0 era, we changed symbols that do not have to be global 201 to file scope static, but a few functions in graph.c were used by 202 CGit from sideways bypassing the entry points of the API the 203 in-tree users use. 204 205 * "git update-index -h" did not do the usual "-h(elp)" thing. 206 207 * "git index-pack" had a buffer-overflow while preparing an 208 informational message when the translated version of it was too 209 long. 210 211 * 'git commit -m "$msg"' used to add an extra newline even when 212 $msg already ended with one. 213 (merge 46fbf75 bc/commit-complete-lines-given-via-m-option later to maint). 214 215 * The SSL peer verification done by "git imap-send" did not ask for 216 Server Name Indication (RFC 4366), failing to connect SSL/TLS 217 sites that serve multiple hostnames on a single IP. 218 219 * perl/Git.pm::cat_blob slurped everything in core only to write it 220 out to a file descriptor, which was not a very smart thing to do. 221 222 * "git branch" did not bother to check nonsense command line 223 parameters and issue errors in many cases. 224 225 * Verification of signed tags were not done correctly when not in C 226 or en/US locale. 227 (merge 0174eea mg/gpg-interface-using-status later to maint). 228 229 * Some platforms and users spell UTF-8 differently; retry with the 230 most official "UTF-8" when the system does not understand the 231 user-supplied encoding name that are the common alternative 232 spellings of UTF-8. 233 234 * When export-subst is used, "zip" output recorded incorrect 235 size of the file. 236 237 * "git am $maildir/" applied messages in an unexpected order; sort 238 filenames read from the maildir/ in a way that is more likely to 239 sort messages in the order the writing MUA meant to, by sorting 240 numeric segment in numeric order and non-numeric segment in 241 alphabetical order. 242 243 * "git submodule update", when recursed into sub-submodules, did not 244 acccumulate the prefix paths.