]>
Commit | Line | Data |
---|---|---|
5bed9f6a JH |
1 | Git v1.7.10.3 Release Notes |
2 | =========================== | |
3 | ||
4 | Fixes since v1.7.10.2 | |
5 | --------------------- | |
6 | ||
c4649188 JH |
7 | * The message file for German translation has been updated a bit. |
8 | ||
5bed9f6a JH |
9 | * Running "git checkout" on an unborn branch used to corrupt HEAD. |
10 | ||
11 | * When checking out another commit from an already detached state, we | |
12 | used to report all commits that are not reachable from any of the | |
13 | refs as lossage, but some of them might be reachable from the new | |
14 | HEAD, and there is no need to warn about them. | |
15 | ||
16 | * Some time ago, "git clone" lost the progress output for its | |
17 | "checkout" phase; when run without any "--quiet" option, it should | |
18 | give progress to the lengthy operation. | |
19 | ||
26e5c5d0 JH |
20 | * The directory path used in "git diff --no-index", when it recurses |
21 | down, was broken with a recent update after v1.7.10.1 release. | |
22 | ||
5bed9f6a JH |
23 | * "log -z --pretty=tformat:..." did not terminate each record with |
24 | NUL. The fix is not entirely correct when the output also asks for | |
25 | --patch and/or --stat, though. | |
26 | ||
27 | * The DWIM behaviour for "log --pretty=format:%gd -g" was somewhat | |
28 | broken and gave undue precedence to configured log.date, causing | |
29 | "git stash list" to show "stash@{time stamp string}". | |
30 | ||
26e5c5d0 JH |
31 | * "git status --porcelain" ignored "--branch" option by mistake. The |
32 | output for "git status --branch -z" was also incorrect and did not | |
33 | terminate the record for the current branch name with NUL as asked. | |
34 | ||
35 | * When a submodule repository uses alternate object store mechanism, | |
36 | some commands that were started from the superproject did not | |
37 | notice it and failed with "No such object" errors. The subcommands | |
38 | of "git submodule" command that recursed into the submodule in a | |
39 | separate process were OK; only the ones that cheated and peeked | |
40 | directly into the submodule's repository from the primary process | |
41 | were affected. | |
42 | ||
5bed9f6a | 43 | Also contains minor fixes and documentation updates. |