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 36 37Foreign Interface 38 39 40 41Performance, Internal Implementation, etc. 42 43 * Updates for building under msvc. 44 45 46Also contains minor documentation updates and code clean-ups. 47 48 49Fixes since v1.8.2 50------------------ 51 52Unless otherwise noted, all the fixes since v1.8.2 in the maintenance 53track are contained in this release (see release notes to them for 54details). 55 56 * The "--color=<when>" argument to the commands in the diff family 57 was described poorly. 58 (merge 3d0e75f jc/color-diff-doc later to maint). 59 60 * The arguments given to pre-rebase hook were not documented. 61 (merge 0414acc wk/doc-pre-rebase later to maint). 62 63 * The v4 index format was not documented. 64 (merge 647d879 nd/doc-index-format later to maint). 65 66 * The "--match=<pattern>" argument "git describe" takes uses glob 67 pattern but it wasn't obvious from the documentation. 68 (merge 5229149 gp/describe-match-uses-glob-pattern later to maint). 69 70 * Some sources failed to compile on systems that lack NI_MAXHOST in 71 their system header (e.g. z/OS). 72 (merge 3b130ade dm/ni-maxhost-may-be-missing later to maint). 73 74 * Add an example use of "--env-filter" in "filter-branch" 75 documentation. 76 (merge 21b6e4f tk/doc-filter-branch later to maint). 77 78 * "git bundle verify" did not say "records a complete history" for a 79 bundle that does not have any prerequisites. 80 (merge a02ffe0 lf/bundle-verify-list-prereqs later to maint). 81 82 * In the v1.8.0 era, we changed symbols that do not have to be global 83 to file scope static, but a few functions in graph.c were used by 84 CGit from sideways bypassing the entry points of the API the 85 in-tree users use. 86 (merge ac751a0 jk/graph-c-expose-symbols-for-cgit later to maint).