projects / thirdparty / git.git / blame
| Commit | Line | Data |
|---|---|---|
| 7ad0f27b JH |
1 | GIT v1.5.6.2 Release Notes |
| 2 | ========================== | |
| 3 | ||
| 4 | Futureproof | |
| 5 | ----------- | |
| 6 | ||
| 7 | * "git-shell" accepts requests without a dash between "git" and | |
| 8 | subcommand name (e.g. "git upload-pack") which the newer client will | |
| 9 | start to make sometime in the future. | |
| 10 | ||
| 11 | Fixes since v1.5.6.1 | |
| 12 | -------------------- | |
| 13 | ||
| 78e31186 JH |
14 | * "git clone" from a remote that is named with url.insteadOf setting in |
| 15 | $HOME/.gitconfig did not work well. | |
| 7ad0f27b | 16 | |
| 78e31186 JH |
17 | * "git describe --long --tags" segfaulted when the described revision was |
| 18 | tagged with a lightweight tag. | |
| 7ad0f27b JH |
19 | |
| 20 | * "git diff --check" did not report the result via its exit status | |
| 21 | reliably. | |
| 22 | ||
| 78e31186 JH |
23 | * When remote side used to have branch 'foo' and git-fetch finds that now |
| 24 | it has branch 'foo/bar', it refuses to lose the existing remote tracking | |
| 25 | branch and its reflog. The error message has been improved to suggest | |
| 26 | pruning the remote if the user wants to proceed and get the latest set | |
| 27 | of branches from the remote, including such 'foo/bar'. | |
| 28 | ||
| 29 | * "git reset file" should mean the same thing as "git reset HEAD file", | |
| 30 | but we required disambiguating -- even when "file" is not ambiguous. | |
| 31 | ||
| 7ad0f27b JH |
32 | * "git show" segfaulted when an annotated tag that points at another |
| 33 | annotated tag was given to it. | |
| 34 | ||
| 78e31186 JH |
35 | * Optimization for a large import via "git-svn" introduced in v1.5.6 had a |
| 36 | serious memory and temporary file leak, which made it unusable for | |
| 37 | moderately large import. | |
| 38 | ||
| 39 | * "git-svn" mangled remote nickname used in the configuration file | |
| 40 | unnecessarily. |