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 56Foreign Interface 57 58 59 60Performance, Internal Implementation, etc. 61 62 * Updates for building under msvc. 63 64 * A few codepaths knew how much data they need to put in the 65 hashtables they use upfront, but still started from a small table 66 repeatedly growing and rehashing. 67 68 69Also contains minor documentation updates and code clean-ups. 70 71 72Fixes since v1.8.2 73------------------ 74 75Unless otherwise noted, all the fixes since v1.8.2 in the maintenance 76track are contained in this release (see release notes to them for 77details). 78 79 * Clarify in the documentation "what" gets pushed to "where" when the 80 command line to "git push" does not say these explicitly. 81 (merge cfe1348 jc/maint-push-refspec-default-doc later to maint). 82 83 * The "--color=<when>" argument to the commands in the diff family 84 was described poorly. 85 (merge 3d0e75f jc/color-diff-doc later to maint). 86 87 * The arguments given to pre-rebase hook were not documented. 88 (merge 0414acc wk/doc-pre-rebase later to maint). 89 90 * The v4 index format was not documented. 91 (merge 647d879 nd/doc-index-format later to maint). 92 93 * The "--match=<pattern>" argument "git describe" takes uses glob 94 pattern but it wasn't obvious from the documentation. 95 (merge 5229149 gp/describe-match-uses-glob-pattern later to maint). 96 97 * Some sources failed to compile on systems that lack NI_MAXHOST in 98 their system header (e.g. z/OS). 99 (merge 3b130ade dm/ni-maxhost-may-be-missing later to maint). 100 101 * Add an example use of "--env-filter" in "filter-branch" 102 documentation. 103 (merge 21b6e4f tk/doc-filter-branch later to maint). 104 105 * "git bundle verify" did not say "records a complete history" for a 106 bundle that does not have any prerequisites. 107 (merge a02ffe0 lf/bundle-verify-list-prereqs later to maint). 108 109 * In the v1.8.0 era, we changed symbols that do not have to be global 110 to file scope static, but a few functions in graph.c were used by 111 CGit from sideways bypassing the entry points of the API the 112 in-tree users use. 113 (merge ac751a0 jk/graph-c-expose-symbols-for-cgit later to maint). 114 115 * "git update-index -h" did not do the usual "-h(elp)" thing. 116 117 * "git index-pack" had a buffer-overflow while preparing an 118 informational message when the translated version of it was too 119 long. 120 (merge 5c3459f nd/index-pack-l10n-buf-overflow later to maint). 121 122 * 'git commit -m "$msg"' used to add an extra newline even when 123 $msg already ended with one. 124 (merge 46fbf75 bc/commit-complete-lines-given-via-m-option later to maint). 125 126 * The SSL peer verification done by "git imap-send" did not ask for 127 Server Name Indication (RFC 4366), failing to connect SSL/TLS 128 sites that serve multiple hostnames on a single IP. 129 (merge 698a1ec ob/imap-send-ssl-verify later to maint). 130 131 * perl/Git.pm::cat_blob slurped everything in core only to write it 132 out to a file descriptor, which was not a very smart thing to do. 133 (merge 712c6ad jc/perl-cat-blob later to maint). 134 135 * "git branch" did not bother to check nonsense command line 136 parameters and issue errors in many cases. 137 (merge 8efb889 nd/branch-error-cases later to maint). 138 139 * Verification of signed tags were not done correctly when not in C 140 or en/US locale. 141 (merge 0174eea mg/gpg-interface-using-status later to maint). 142 143 * Some platforms and users spell UTF-8 differently; retry with the 144 most official "UTF-8" when the system does not understand the 145 user-supplied encoding name that are the common alternative 146 spellings of UTF-8. 147 (merge 5c680be jk/utf-8-can-be-spelled-differently later to maint). 148 149 * When export-subst is used, "zip" output recorded incorrect 150 size of the file. 151 (merge d3c1472 rs/zip-compresssed-size-with-export-subst later to maint). 152 153 * "git am $maildir/" applied messages in an unexpected order; sort 154 filenames read from the maildir/ in a way that is more likely to 155 sort messages in the order the writing MUA meant to, by sorting 156 numeric segment in numeric order and non-numeric segment in 157 alphabetical order. 158 (merge 18505c3 jk/mailsplit-maildir-muttsort later to maint). 159 160 * "git submodule update", when recursed into sub-submodules, did not 161 acccumulate the prefix paths. 162 (merge 75bf5e6 we/submodule-update-prefix-output later to maint).