| 1 | Git 1.7.12.3 Release Notes |
| 2 | ========================== |
| 3 | |
| 4 | Fixes since v1.7.12.2 |
| 5 | --------------------- |
| 6 | |
| 7 | * "git am" mishandled a patch attached as application/octet-stream |
| 8 | (e.g. not text/*); Content-Transfer-Encoding (e.g. base64) was not |
| 9 | honored correctly. |
| 10 | |
| 11 | * It was unclear in the documentation for "git blame" that it is |
| 12 | unnecessary for users to use the "--follow" option. |
| 13 | |
| 14 | * A repository created with "git clone --single" had its fetch |
| 15 | refspecs set up just like a clone without "--single", leading the |
| 16 | subsequent "git fetch" to slurp all the other branches, defeating |
| 17 | the whole point of specifying "only this branch". |
| 18 | |
| 19 | * "git fetch" over http had an old workaround for an unlikely server |
| 20 | misconfiguration; it turns out that this hurts debuggability of the |
| 21 | configuration in general, and has been reverted. |
| 22 | |
| 23 | * "git fetch" over http advertised that it supports "deflate", which |
| 24 | is much less common, and did not advertise the more common "gzip" on |
| 25 | its Accept-Encoding header. |
| 26 | |
| 27 | * "git receive-pack" (the counterpart to "git push") did not give |
| 28 | progress output while processing objects it received to the user |
| 29 | when run over the smart-http protocol. |
| 30 | |
| 31 | * "git status" honored the ignore=dirty settings in .gitmodules but |
| 32 | "git commit" didn't. |
| 33 | |
| 34 | Also contains a handful of documentation updates. |