|
| 1 | +GIT v1.6.1.2 Release Notes |
| 2 | +========================== |
| 3 | + |
| 4 | +Fixes since v1.6.1.1 |
| 5 | +-------------------- |
| 6 | + |
| 7 | +* The logic for rename detectin in internal diff used by commands like |
| 8 | + "git diff" and "git blame" have been optimized to avoid loading the same |
| 9 | + blob repeatedly. |
| 10 | + |
| 11 | +* We did not allow writing out a blob that is larger than 2GB for no good |
| 12 | + reason. |
| 13 | + |
| 14 | +* "git format-patch -o $dir", when $dir is a relative directory, used it |
| 15 | + as relative to the root of the work tree, not relative to the current |
| 16 | + directory. |
| 17 | + |
| 18 | +* v1.6.1 introduced an optimization for "git push" into a repository (A) |
| 19 | + that borrows its objects from another repository (B) to avoid sending |
| 20 | + objects that are available in repository B, when they are not yet used |
| 21 | + by repository A. However the code on the "git push" sender side was |
| 22 | + buggy and did not work when repository B had new objects that are not |
| 23 | + known by the sender. This caused pushing into a "forked" repository |
| 24 | + served by v1.6.1 software using "git push" from v1.6.1 sometimes did not |
| 25 | + work. The bug was purely on the "git push" sender side, and has been |
| 26 | + corrected. |
| 27 | + |
| 28 | +* "git status -v" did not paint its diff output in colour even when |
| 29 | + color.ui configuration was set. |
| 30 | + |
| 31 | +* "git ls-tree" learned --full-tree option to help Porcelain scripts that |
| 32 | + want to always see the full path regardless of the current working |
| 33 | + directory. |
| 34 | + |
| 35 | +* "git grep" incorrectly searched in work tree paths even when they are |
| 36 | + marked as assume-unchanged. It now searches in the index entries. |
| 37 | + |
| 38 | +* "git gc" with no grace period needlessly ejected packed but unreachable |
| 39 | + objects in their loose form, only to delete them right away. |
0 commit comments