|
| 1 | +Git v1.6.5.3 Release Notes |
| 2 | +========================== |
| 3 | + |
| 4 | +Fixes since v1.6.5.2 |
| 5 | +-------------------- |
| 6 | + |
| 7 | + * info/grafts file didn't ignore trailing CR at the end of lines. |
| 8 | + |
| 9 | + * Packages generated on newer FC were unreadable by older versions of |
| 10 | + RPM as the new default is to use stronger hash. |
| 11 | + |
| 12 | + * output from "git blame" was unreadable when the file ended in an |
| 13 | + incomplete line. |
| 14 | + |
| 15 | + * "git add -i/-p" didn't handle deletion of empty files correctly. |
| 16 | + |
| 17 | + * "git clone" takes up to two parameters, but did not complain when |
| 18 | + given more arguments than necessary and silently ignored them. |
| 19 | + |
| 20 | + * "git cvsimport" did not read files given as command line arguments |
| 21 | + correctly when it is run from a subdirectory. |
| 22 | + |
| 23 | + * "git diff --color-words -U0" didn't work correctly. |
| 24 | + |
| 25 | + * The handling of blank lines at the end of file by "git diff/apply |
| 26 | + --whitespace" was inconsistent with the other kinds of errors. |
| 27 | + They are now colored, warned against, and fixed the same way as others. |
| 28 | + |
| 29 | + * There was no way to allow blank lines at the end of file without |
| 30 | + allowing extra blanks at the end of lines. You can use blank-at-eof |
| 31 | + and blank-at-eol whitespace error class to specify them separately. |
| 32 | + The old trailing-space error class is now a short-hand to set both. |
| 33 | + |
| 34 | + * "-p" option to "git format-patch" was supposed to suppress diffstat |
| 35 | + generation, but it was broken since 1.6.1. |
| 36 | + |
| 37 | + * "git imap-send" did not compile cleanly with newer OpenSSL. |
| 38 | + |
| 39 | + * "git help -a" outside of a git repository was broken. |
| 40 | + |
| 41 | + * "git ls-files -i" was supposed to be inverse of "git ls-files" without -i |
| 42 | + with respect to exclude patterns, but it was broken since 1.6.5.2. |
| 43 | + |
| 44 | + * "git ls-remote" outside of a git repository over http was broken. |
| 45 | + |
| 46 | + * "git rebase -i" gave bogus error message when the command word was |
| 47 | + misspelled. |
| 48 | + |
| 49 | + * "git receive-pack" that is run in response to "git push" did not run |
| 50 | + garbage collection nor update-server-info, but in larger hosting sites, |
| 51 | + these almost always need to be run. To help site administrators, the |
| 52 | + command now runs "gc --auto" and "u-s-i" by setting receive.autogc |
| 53 | + and receive.updateserverinfo configuration variables, respectively. |
| 54 | + |
| 55 | + * Release notes spelled the package name with incorrect capitalization. |
| 56 | + |
| 57 | + * "gitweb" did not escape non-ascii characters correctly in the URL. |
| 58 | + |
| 59 | + * "gitweb" showed "patch" link even for merge commits. |
| 60 | + |
| 61 | + * "gitweb" showed incorrect links for blob line numbers in pathinfo mode. |
| 62 | + |
| 63 | +Other minor documentation updates are included. |
0 commit comments