v1.5.0.txt: Post -rc2 updates

Junio C Hamano committed Jan 29, 2007 at 02:47 UTC 8fb5b9db666db16dd235a0d0b18aa48dd00c2638
1 file changed +45
v1.5.0.txt
+45
@@ -168,9 +168,19 @@ Updates in v1.5.0 since v1.4.4 series
168 accumulated too many small packs this way as well. Updated
169 git-count-objects helps you with this.
170
171 + - git-fetch also more agressively keeps the transferred objects
172 + packed. This behaviour of git-push and git-fetch can be
173 + tweaked with a single configuration transfer.unpacklimit (but
174 + usually there should not be any need for a user to tweak it).
175 +
176 - A new command, git-remote, can help you manage your remote
177 tracking branch definitions.
178
179 + - You may need to specify explicit paths for upload-pack and/or
180 + receive-pack due to your ssh daemon configuration on the
181 + other end. This can now be done via remote.*.uploadpack and
182 + remote.*.receivepack configuration.
183 +
184
185 * Bare repositories
186
@@ -238,6 +248,12 @@ Updates in v1.5.0 since v1.4.4 series
248 'git-reflog expire', 'git-pack-refs --prune', and 'git-rerere
249 gc'.
250
251 + - The output from fsck ("fsck-objects" is called just "fsck"
252 + now, but the old name continues to work) was needlessly
253 + alarming in that it warned missing objects that are reachable
254 + only from dangling objects. This has been corrected and the
255 + output is much more useful.
256 +
257
258 * Detached HEAD
259
@@ -289,6 +305,35 @@ Updates in v1.5.0 since v1.4.4 series
305 color.* namespace (older diff.color.*, status.color.* are
306 still supported).
307
308 + - 'git-repo-config' command is accessible as 'git-config' now.
309 +
310 +
311 +* Updated features
312 +
313 + - git-describe uses better criteria to pick a base ref. It
314 + used to pick the one with the newest timestamp, but now it
315 + picks the one that is topologically the closest (that is,
316 + among ancestors of commit C, the ref T that has the shortest
317 + output from "git-rev-list T..C" is chosen).
318 +
319 + - git-describe gives the number of commits since the base ref
320 + between the refname and the hash suffix. E.g. the commit one
321 + before v2.6.20-rc6 in the kernel repository is:
322 +
323 + v2.6.20-rc5-306-ga21b069
324 +
325 + which tells you that its object name begins with a21b069,
326 + v2.6.20-rc5 is an ancestor of it (meaning, the commit
327 + contains everything -rc5 has), and there are 306 commits
328 + since v2.6.20-rc5.
329 +
330 + - git-describe with --abbrev=0 can be used to show only the
331 + name of the base ref.
332 +
333 + - git-blame learned a new option, --incremental, that tells it
334 + to output the blames as they are assigned. A sample script
335 + to use it is also included as contrib/blameview.
336 +
337
338 * Less external dependency
339