|
| 1 | +Git 1.8.1.5 Release Notes |
| 2 | +========================= |
| 3 | + |
| 4 | +Fixes since v1.8.1.5 |
| 5 | +-------------------- |
| 6 | + |
| 7 | + * "git apply --summary" has been taught to make sure the similarity |
| 8 | + value shown in its output is sensible, even when the input had a |
| 9 | + bogus value. |
| 10 | + |
| 11 | + * "git clean" showed what it was going to do, but sometimes ended |
| 12 | + up finding that it was not allowed to do so, which resulted in a |
| 13 | + confusing output (e.g. after saying that it will remove an |
| 14 | + untracked directory, it found an embedded git repository there |
| 15 | + which it is not allowed to remove). It now performs the actions |
| 16 | + and then reports the outcome more faithfully. |
| 17 | + |
| 18 | + * "git clone" used to allow --bare and --separate-git-dir=$there |
| 19 | + options at the same time, which was nonsensical. |
| 20 | + |
| 21 | + * "git cvsimport" mishandled timestamps at DST boundary. |
| 22 | + |
| 23 | + * We used to have an arbitrary 32 limit for combined diff input, |
| 24 | + resulting in incorrect number of leading colons shown when showing |
| 25 | + the "--raw --cc" output. |
| 26 | + |
| 27 | + * The smart HTTP clients forgot to verify the content-type that comes |
| 28 | + back from the server side to make sure that the request is being |
| 29 | + handled properly. |
| 30 | + |
| 31 | + * "git help remote-helpers" failed to find the documentation. |
| 32 | + |
| 33 | + * "gitweb" pages served over HTTPS, when configured to show picon or |
| 34 | + gravatar, referred to these external resources to be fetched via |
| 35 | + HTTP, resulting in mixed contents warning in browsers. |
| 36 | + |
| 37 | +Also contains various documentation fixes. |
0 commit comments