Skip to content
Browse files


Signed-off-by: Junio C Hamano <>
  • Loading branch information...
1 parent a9ed6ce commit b296e8fce6de6a40a41b5168dfbe735d11255256 @gitster gitster committed Jan 29, 2009
Showing with 41 additions and 2 deletions.
  1. +39 −0 Documentation/RelNotes-
  2. +1 −1 GIT-VERSION-GEN
  3. +1 −1 RelNotes
39 Documentation/RelNotes-
@@ -0,0 +1,39 @@
+GIT v1.6.1.2 Release Notes
+Fixes since v1.6.1.1
+* The logic for rename detectin in internal diff used by commands like
+ "git diff" and "git blame" have been optimized to avoid loading the same
+ blob repeatedly.
+* We did not allow writing out a blob that is larger than 2GB for no good
+ reason.
+* "git format-patch -o $dir", when $dir is a relative directory, used it
+ as relative to the root of the work tree, not relative to the current
+ directory.
+* v1.6.1 introduced an optimization for "git push" into a repository (A)
+ that borrows its objects from another repository (B) to avoid sending
+ objects that are available in repository B, when they are not yet used
+ by repository A. However the code on the "git push" sender side was
+ buggy and did not work when repository B had new objects that are not
+ known by the sender. This caused pushing into a "forked" repository
+ served by v1.6.1 software using "git push" from v1.6.1 sometimes did not
+ work. The bug was purely on the "git push" sender side, and has been
+ corrected.
+* "git status -v" did not paint its diff output in colour even when
+ color.ui configuration was set.
+* "git ls-tree" learned --full-tree option to help Porcelain scripts that
+ want to always see the full path regardless of the current working
+ directory.
+* "git grep" incorrectly searched in work tree paths even when they are
+ marked as assume-unchanged. It now searches in the index entries.
+* "git gc" with no grace period needlessly ejected packed but unreachable
+ objects in their loose form, only to delete them right away.
@@ -1,7 +1,7 @@
2 RelNotes

0 comments on commit b296e8f

Please sign in to comment.
Something went wrong with that request. Please try again.