1Git 2.12 Release Notes 2====================== 3 4Backward compatibility notes. 5 6 * Use of an empty string that is used for 'everything matches' is 7 still warned and Git asks users to use a more explicit '.' for that 8 instead. The hope is that existing users will not mind this 9 change, and eventually the warning can be turned into a hard error, 10 upgrading the deprecation into removal of this (mis)feature. That 11 is not scheduled to happen in the upcoming release (yet). 12 13 * The historical argument order "git merge <msg> HEAD <commit>..." 14 has been deprecated for quite some time, and will be removed in the 15 upcoming release. 16 17 18Updates since v2.11 19------------------- 20 21UI, Workflows & Features 22 23 * 24 25 26Performance, Internal Implementation, Development Support etc. 27 28 * 29 30 31Also contains various documentation updates and code clean-ups. 32 33 * 34 35 36Fixes since v2.10 37----------------- 38 39Unless otherwise noted, all the fixes since v2.9 in the maintenance 40track are contained in this release (see the maintenance releases' 41notes for details). 42 43 * We often decide if a session is interactive by checking if the 44 standard I/O streams are connected to a TTY, but isatty() that 45 comes with Windows incorrectly returned true if it is used on NUL 46 (i.e. an equivalent to /dev/null). This has been fixed. 47 (merge cbb3f3c9b1 js/mingw-isatty later to maint). 48 49 * "git svn" did not work well with path components that are "0", and 50 some configuration variable it uses were not documented. 51 (merge ea9a93dcc2 ew/svn-fixes later to maint). 52 53 * Other minor doc, test and build updates and code cleanups.