|
| 1 | +Git v1.8.5.5 Release Notes |
| 2 | +========================== |
| 3 | + |
| 4 | +Fixes since v1.8.5.4 |
| 5 | +-------------------- |
| 6 | + |
| 7 | + * The pathspec matching code, while comparing two trees (e.g. "git |
| 8 | + diff A B -- path1 path2") was too aggressive and failed to match |
| 9 | + some paths when multiple pathspecs were involved. |
| 10 | + |
| 11 | + * "git repack --max-pack-size=8g" stopped being parsed correctly when |
| 12 | + the command was reimplemented in C. |
| 13 | + |
| 14 | + * A recent update to "git send-email" broke platforms where |
| 15 | + /etc/ssl/certs/ directory exists but cannot be used as SSL_ca_path |
| 16 | + (e.g. Fedora rawhide). |
| 17 | + |
| 18 | + * A handful of bugs around interpreting $branch@{upstream} notation |
| 19 | + and its lookalike, when $branch part has interesting characters, |
| 20 | + e.g. "@", and ":", have been fixed. |
| 21 | + |
| 22 | + * "git clone" would fail to clone from a repository that has a ref |
| 23 | + directly under "refs/", e.g. "refs/stash", because different |
| 24 | + validation paths do different things on such a refname. Loosen the |
| 25 | + client side's validation to allow such a ref. |
| 26 | + |
| 27 | + * "git log --left-right A...B" lost the "leftness" of commits |
| 28 | + reachable from A when A is a tag as a side effect of a recent |
| 29 | + bugfix. This is a regression in 1.8.4.x series. |
| 30 | + |
| 31 | + * "git merge-base --octopus" used to leave cleaning up suboptimal |
| 32 | + result to the caller, but now it does the clean-up itself. |
| 33 | + |
| 34 | + * "git mv A B/", when B does not exist as a directory, should error |
| 35 | + out, but it didn't. |
| 36 | + |
| 37 | +Also contains typofixes, documentation updates and trivial code clean-ups. |
0 commit comments