|
| 1 | +Git 1.7.12.2 Release Notes |
| 2 | +========================== |
| 3 | + |
| 4 | +Fixes since v1.7.12.1 |
| 5 | +--------------------- |
| 6 | + |
| 7 | + * Even during a conflicted merge, "git blame $path" always meant to |
| 8 | + blame uncommitted changes to the "working tree" version; make it |
| 9 | + more useful by showing cleanly merged parts as coming from the other |
| 10 | + branch that is being merged. |
| 11 | + |
| 12 | + * "git blame MAKEFILE" run in a history that has "Makefile" but not |
| 13 | + "MAKEFILE" should say "No such file MAKEFILE in HEAD", but got |
| 14 | + confused on a case insensitive filesystem and failed to do so. |
| 15 | + |
| 16 | + * "git fetch --all", when passed "--no-tags", did not honor the |
| 17 | + "--no-tags" option while fetching from individual remotes (the same |
| 18 | + issue existed with "--tags", but combination "--all --tags" makes |
| 19 | + much less sense than "--all --no-tags"). |
| 20 | + |
| 21 | + * "git log/diff/format-patch --stat" showed the "N line(s) added" |
| 22 | + comment in user's locale and caused careless submitters to send |
| 23 | + patches with such a line in them to projects whose project language |
| 24 | + is not their language, mildly irritating others. Localization to |
| 25 | + the line has been disabled for now. |
| 26 | + |
| 27 | + * The subcommand to remove the definition of a remote in "git remote" |
| 28 | + was named "rm" even though all other subcommands were spelled out. |
| 29 | + Introduce "git remote remove" to remove confusion, and keep "rm" as |
| 30 | + a backward compatible synonym. |
| 31 | + |
| 32 | +Also contains a handful of documentation updates. |
0 commit comments