1Git v1.8.2.1 Release Notes 2========================== 3 4Fixes since v1.8.2 5------------------ 6 7 * Verification of signed tags were not done correctly when not in C 8 or en/US locale. 9 10 * 'git commit -m "$msg"' used to add an extra newline even when 11 $msg already ended with one. 12 13 * The "--match=<pattern>" option of "git describe", when used with 14 "--all" to allow refs that are not annotated tags to be used as a 15 base of description, did not restrict the output from the command 16 to those that match the given pattern. 17 18 * An aliased command spawned from a bare repository that does not say 19 it is bare with "core.bare = yes" is treated as non-bare by mistake. 20 21 * When "format-patch" quoted a non-ascii strings on the header files, 22 it incorrectly applied rfc2047 and chopped a single character in 23 the middle of it. 24 25 * "git archive" reports a failure when asked to create an archive out 26 of an empty tree. It would be more intuitive to give an empty 27 archive back in such a case. 28 29 * "git tag -f <tag>" always said "Updated tag '<tag>'" even when 30 creating a new tag (i.e. not overwriting nor updating). 31 32 * "git cmd -- ':(top'" was not diagnosed as an invalid syntax, and 33 instead the parser kept reading beyond the end of the string. 34 35 * Annotated tags outside refs/tags/ hierarchy were not advertised 36 correctly to the ls-remote and fetch with recent version of Git. 37 38 * The code to keep track of what directory names are known to Git on 39 platforms with case insensitive filesystems can get confused upon a 40 hash collision between these pathnames and looped forever. 41 42 * The logic used by "git diff -M --stat" to shorten the names of 43 files before and after a rename did not work correctly when the 44 common prefix and suffix between the two filenames overlapped. 45 46 * "git submodule update", when recursed into sub-submodules, did not 47 acccumulate the prefix paths. 48 49 * "git am $maildir/" applied messages in an unexpected order; sort 50 filenames read from the maildir/ in a way that is more likely to 51 sort messages in the order the writing MUA meant to, by sorting 52 numeric segment in numeric order and non-numeric segment in 53 alphabetical order. 54 55 * When export-subst is used, "zip" output recorded incorrect 56 size of the file. 57 58 * Some platforms and users spell UTF-8 differently; retry with the 59 most official "UTF-8" when the system does not understand the 60 user-supplied encoding name that are the common alternative 61 spellings of UTF-8. 62 63 * "git branch" did not bother to check nonsense command line 64 parameters and issue errors in many cases. 65 66 * "git update-index -h" did not do the usual "-h(elp)" thing. 67 68 * perl/Git.pm::cat_blob slurped everything in core only to write it 69 out to a file descriptor, which was not a very smart thing to do. 70 71 * The SSL peer verification done by "git imap-send" did not ask for 72 Server Name Indication (RFC 4366), failing to connect SSL/TLS 73 sites that serve multiple hostnames on a single IP. 74 75 * "git index-pack" had a buffer-overflow while preparing an 76 informational message when the translated version of it was too 77 long. 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 82 * In "git reflog expire", REACHABLE bit was not cleared from the 83 correct objects. 84 85 * The "--color=<when>" argument to the commands in the diff family 86 was described poorly. 87 88 * The arguments given to pre-rebase hook were not documented. 89 90 * The v4 index format was not documented. 91 92 * The "--match=<pattern>" argument "git describe" takes uses glob 93 pattern but it wasn't obvious from the documentation. 94 95 * Some sources failed to compile on systems that lack NI_MAXHOST in 96 their system header (e.g. z/OS). 97 98 * Add an example use of "--env-filter" in "filter-branch" 99 documentation. 100 101 * "git bundle verify" did not say "records a complete history" for a 102 bundle that does not have any prerequisites. 103 104 * In the v1.8.0 era, we changed symbols that do not have to be global 105 to file scope static, but a few functions in graph.c were used by 106 CGit from sideways bypassing the entry points of the API the 107 in-tree users use. 108 109 * "git merge-tree" had a typo in the logic to detect d/f conflicts, 110 which caused it to segfault in some cases.