@@ -116,6 +116,35 @@ Unless otherwise noted, all the fixes since v1.7.12 in the
116
116
maintenance track are contained in this release (see release notes
117
117
to them for details).
118
118
119
+ * "git blame MAKEFILE" run in a history that has "Makefile" but not
120
+ "MAKEFILE" should say "No such file MAKEFILE in HEAD", but got
121
+ confused on a case insensitive filesystem and failed to do so.
122
+ (merge 9aeaab6 jc/maint-blame-no-such-path later to maint).
123
+
124
+ * Even during a conflicted merge, "git blame $path" always meant to
125
+ blame uncommitted changes to the "working tree" version; make it
126
+ more useful by showing cleanly merged parts as coming from the other
127
+ branch that is being merged.
128
+ (merge 9aeaab6 jc/maint-blame-no-such-path later to maint).
129
+
130
+ * Documentation talked about "first line of commit log" when it meant
131
+ the title of the commit. The description was clarified by defining
132
+ how the title is decided and rewording the casual mention of "first
133
+ line" to "title".
134
+ (merge 52ffe99 jw/doc-commit-title later to maint).
135
+
136
+ * The attribute system may be asked for a path that itself or its
137
+ leading directories no longer exists in the working tree. Failure
138
+ to open per-directory .gitattributes with error status other than
139
+ ENOENT and ENOTDIR are diagnosed.
140
+ (merge 8e950da jk/config-warn-on-inaccessible-paths later to maint).
141
+
142
+ * Earlier we made the diffstat summary line that shows the number of
143
+ lines added/deleted localizable, but it was found irritating having
144
+ to see them in various languages on a list whose discussion language
145
+ is English.
146
+ (merge 218adaa nd/maint-diffstat-summary later to maint).
147
+
119
148
* "git fetch --all", when passed "--no-tags", did not honor the
120
149
"--no-tags" option while fetching from individual remotes (the same
121
150
issue existed with "--tags", but combination "--all --tags" makes
0 commit comments