|
| 1 | +Git v1.8.4.2 Release Notes |
| 2 | +======================== |
| 3 | + |
| 4 | +Fixes since v1.8.4.1 |
| 5 | +-------------------- |
| 6 | + |
| 7 | + * When running "fetch -q", a long silence while the sender side |
| 8 | + computes the set of objects to send can be mistaken by proxies as |
| 9 | + dropped connection. The server side has been taught to send a |
| 10 | + small empty messages to keep the connection alive. |
| 11 | + |
| 12 | + * When the webserver responds with "405 Method Not Allowed", "git |
| 13 | + http-backend" should tell the client what methods are allowed with |
| 14 | + the "Allow" header. |
| 15 | + |
| 16 | + * "git cvsserver" computed the permission mode bits incorrectly for |
| 17 | + executable files. |
| 18 | + |
| 19 | + * The implementation of "add -i" has a crippling code to work around |
| 20 | + ActiveState Perl limitation but it by mistake also triggered on Git |
| 21 | + for Windows where MSYS perl is used. |
| 22 | + |
| 23 | + * We made sure that we notice the user-supplied GIT_DIR is actually a |
| 24 | + gitfile, but did not do the same when the default ".git" is a |
| 25 | + gitfile. |
| 26 | + |
| 27 | + * When an object is not found after checking the packfiles and then |
| 28 | + loose object directory, read_sha1_file() re-checks the packfiles to |
| 29 | + prevent racing with a concurrent repacker; teach the same logic to |
| 30 | + has_sha1_file(). |
| 31 | + |
| 32 | + * "git commit --author=$name", when $name is not in the canonical |
| 33 | + "A. U. Thor < [email protected]>" format, looks for a matching name |
| 34 | + from existing history, but did not consult mailmap to grab the |
| 35 | + preferred author name. |
| 36 | + |
| 37 | + * The commit object names in the insn sheet that was prepared at the |
| 38 | + beginning of "rebase -i" session can become ambiguous as the |
| 39 | + rebasing progresses and the repository gains more commits. Make |
| 40 | + sure the internal record is kept with full 40-hex object names. |
| 41 | + |
| 42 | + * "git rebase --preserve-merges" internally used the merge machinery |
| 43 | + and as a side effect, left merge summary message in the log, but |
| 44 | + when rebasing, there should not be a need for merge summary. |
| 45 | + |
| 46 | + * "git rebase -i" forgot that the comment character can be |
| 47 | + configurable while reading its insn sheet. |
| 48 | + |
| 49 | +Also contains a handful of trivial code clean-ups, documentation |
| 50 | +updates, updates to the test suite, etc. |
0 commit comments