@@ -71,6 +71,41 @@ Foreign interfaces, subsystems and ports.
71
71
72
72
UI, Workflows & Features
73
73
74
+ * Instead of typing four capital letters "HEAD", you can say "@" now,
75
+ e.g. "git log @".
76
+
77
+ * "git check-ignore" follows the same rule as "git add" and "git
78
+ status" in that the ignore/exclude mechanism does not take effect
79
+ on paths that are already tracked. With "--no-index" option, it
80
+ can be used to diagnose which paths that should have been ignored
81
+ have been mistakenly added to the index.
82
+
83
+ * Some irrelevant "advice" messages that are shared with "git status"
84
+ output have been removed from the commit log template.
85
+
86
+ * "update-refs" learnt a "--stdin" option to read multiple update
87
+ requests and perform them in an all-or-none fashion.
88
+
89
+ * Just like "make -C <directory>", "git -C <directory> ..." tells Git
90
+ to go there before doing anything else.
91
+
92
+ * Just like "git checkout -" knows to check out and "git merge -"
93
+ knows to merge the branch you were previously on, "git cherry-pick"
94
+ now understands "git cherry-pick -" to pick from the previous
95
+ branch.
96
+
97
+ * "git status" now omits the prefix to make its output a comment in a
98
+ commit log editor, which is not necessary for human consumption.
99
+
100
+ * Make "foo^{tag}" to peel a tag to itself, i.e. no-op., and fail if
101
+ "foo" is not a tag. "git rev-parse --verify v1.0^{tag}" would be
102
+ a more convenient way to say "test $(git cat-file -t v1.0) = tag".
103
+
104
+ * "git branch -v -v" (and "git status") did not distinguish among a
105
+ branch that does not build on any other branch, a branch that is in
106
+ sync with the branch it builds on, and a branch that is configured
107
+ to build on some other branch that no longer exists.
108
+
74
109
* A packfile that stores the same object more than once is broken and
75
110
will be rejected by "git index-pack" that is run when receiving
76
111
data over the wire.
@@ -177,6 +212,31 @@ Unless otherwise noted, all the fixes since v1.8.4 in the maintenance
177
212
track are contained in this release (see release notes to them for
178
213
details).
179
214
215
+ * When running "fetch -q", a long silence while the sender side
216
+ computes the set of objects to send can be mistaken by proxies as
217
+ dropped connection. The server side has been taught to send a
218
+ small empty messages to keep the connection alive.
219
+ (merge 115dedd jk/upload-pack-keepalive later to maint).
220
+
221
+ * "git rebase" had a portability regression in v1.8.4 to trigger a
222
+ bug in some BSD shell implementations.
223
+ (merge 99855dd mm/rebase-continue-freebsd-WB later to maint).
224
+
225
+ * "git branch --track" had a minor regression in v1.8.3.2 and later
226
+ that made it impossible to base your local work on anything but a
227
+ local branch of the upstream repository you are tracking from.
228
+ (merge b0f49ff jh/checkout-auto-tracking later to maint).
229
+
230
+ * When the webserver responds with "405 Method Not Allowed", "git
231
+ http-backend" should tell the client what methods are allowed with
232
+ the "Allow" header.
233
+ (merge 9247be0 bc/http-backend-allow-405 later to maint).
234
+
235
+ * When there is no sufficient overlap between old and new history
236
+ during a "git fetch" into a shallow repository, objects that the
237
+ sending side knows the receiving end has were unnecessarily sent.
238
+ (merge f21d2a7 nd/fetch-into-shallow later to maint).
239
+
180
240
* "git cvsserver" computed the permission mode bits incorrectly for
181
241
executable files.
182
242
(merge 1b48d56 jc/cvsserver-perm-bit-fix later to maint).
0 commit comments