|
| 1 | +GIT v1.5.3.7 Release Notes |
| 2 | +========================== |
| 3 | + |
| 4 | +Fixes since v1.5.3.6 |
| 5 | +-------------------- |
| 6 | + |
| 7 | + * git-send-email added 8-bit contents to the payload without |
| 8 | + marking it as 8-bit in a CTE header. |
| 9 | + |
| 10 | + * "git-bundle create a.bndl HEAD" dereferenced the symref and |
| 11 | + did not record the ref as 'HEAD'; this prevented a bundle |
| 12 | + from being used as a normal source of git-clone. |
| 13 | + |
| 14 | + * The code to reject nonsense command line of the form |
| 15 | + "git-commit -a paths..." and "git-commit --interactive |
| 16 | + paths..." were broken. |
| 17 | + |
| 18 | + * Adding a signature that is not ASCII-only to an original |
| 19 | + commit that is ASCII-only would make the result non-ASCII. |
| 20 | + "git-format-patch -s" did not mark such a message correctly |
| 21 | + with MIME encoding header. |
| 22 | + |
| 23 | + * git-add sometimes did not mark the resulting index entry |
| 24 | + stat-clean. This affected only cases when adding the |
| 25 | + contents with the same length as the previously staged |
| 26 | + contents, and the previous staging made the index entry |
| 27 | + "racily clean". |
| 28 | + |
| 29 | + * git-commit did not honor GIT_INDEX_FILE the user had in the |
| 30 | + environment. |
| 31 | + |
| 32 | + * When checking out a revision, git-checkout did not report where the |
| 33 | + updated HEAD is if you happened to have a file called HEAD in the |
| 34 | + work tree. |
| 35 | + |
| 36 | + * "git-rev-list --objects" mishandled a tree that points at a |
| 37 | + submodule. |
| 38 | + |
| 39 | + * "git cvsimport" was not ready for packed refs that "git gc" can |
| 40 | + produce and gave incorrect results. |
| 41 | + |
| 42 | + * Many scripted Porcelains were confused when you happened to have a |
| 43 | + file called "HEAD" in your work tree. |
| 44 | + |
| 45 | +Also it contains updates to the user manual and documentation. |
0 commit comments