|
| 1 | +Git v1.7.2.3 Release Notes |
| 2 | +========================== |
| 3 | + |
| 4 | +Fixes since v1.7.2.2 |
| 5 | +-------------------- |
| 6 | + |
| 7 | + * When people try insane things such as delta-compressing 4GiB files, we |
| 8 | + threw an assertion failure. |
| 9 | + |
| 10 | + * "git archive" gave the full commit ID for "$Format:%h$". |
| 11 | + |
| 12 | + * "git fetch --tags" did not fetch tags when remote.<nick>.tagopt was set |
| 13 | + to --no-tags. The command line option now overrides the configuration |
| 14 | + setting. |
| 15 | + |
| 16 | + * "git for-each-ref --format='%(objectname:short)'" has been completely |
| 17 | + broken for a long time. |
| 18 | + |
| 19 | + * "git gc" incorrectly pruned a rerere record that was created long |
| 20 | + time ago but still is actively and repeatedly used. |
| 21 | + |
| 22 | + * "git log --follow -M -p" was seriously broken in 1.7.2, reporting |
| 23 | + assertion failure. |
| 24 | + |
| 25 | + * Running "git log" with an incorrect option started pager nevertheless, |
| 26 | + forcing the user to dismiss it. |
| 27 | + |
| 28 | + * "git rebase" did not work well when the user has diff.renames |
| 29 | + configuration variable set. |
| 30 | + |
| 31 | + * An earlier (and rather old) fix to "git rebase" against a rebased |
| 32 | + upstream broke a more normal, non rebased upstream case rather badly, |
| 33 | + attempting to re-apply patches that are already accepted upstream. |
| 34 | + |
| 35 | + * "git submodule sync" forgot to update the superproject's config file |
| 36 | + when submodule URL changed. |
| 37 | + |
| 38 | + * "git pack-refs --all --prune" did not remove a directory that has |
| 39 | + become empty. |
| 40 | + |
| 41 | +--- |
| 42 | +exec >/var/tmp/1 |
| 43 | +echo O=$(git describe maint) |
| 44 | +O=v1.7.2.2 |
| 45 | +git shortlog --no-merges $O..maint |
| 46 | +exit 0 |
0 commit comments