|
| 1 | +GIT v1.5.6.3 Release Notes |
| 2 | +========================== |
| 3 | + |
| 4 | +Fixes since v1.5.6.2 |
| 5 | +-------------------- |
| 6 | + |
| 7 | +* Setting GIT_TRACE will report spawning of external process via run_command(). |
| 8 | + |
| 9 | +* Bash completion script did not notice '--' marker on the command |
| 10 | + line and tried the relatively slow "ref completion" even when |
| 11 | + completing arguments after one. |
| 12 | + |
| 13 | +* Registering a non-empty blob racily and then truncating the working |
| 14 | + tree file for it confused "racy-git avoidance" logic into thinking |
| 15 | + that the path is now unchanged. |
| 16 | + |
| 17 | +* "git clone" had a leftover debugging fprintf(). |
| 18 | + |
| 19 | +* "git clone -q" was not quiet enough as it used to and gave object count |
| 20 | + and progress reports. |
| 21 | + |
| 22 | +* "git clone" marked downloaded packfile with .keep; this could be a |
| 23 | + good thing if the remote side is well packed but otherwise not, |
| 24 | + especially for a project that is not really big. |
| 25 | + |
| 26 | +* The section that describes attributes related to git-archive were placed |
| 27 | + in a wrong place in the gitattributes(5) manual page. |
| 28 | + |
| 29 | +* When "git push" tries to remove a remote ref, and corresponding |
| 30 | + tracking ref is missing, we used to report error (i.e. failure to |
| 31 | + remove something that does not exist). |
| 32 | + |
| 33 | +* "git mailinfo" (hence "git am") did not handle commit log messages in a |
| 34 | + MIME multipart mail correctly. |
| 35 | + |
| 36 | +Contains other various documentation fixes. |
| 37 | + |
| 38 | +-- |
| 39 | +exec >/var/tmp/1 |
| 40 | +O=v1.5.6.2-23-ge965647 |
| 41 | +echo O=$(git describe maint) |
| 42 | +git shortlog --no-merges $O..maint |
0 commit comments