]>
Commit | Line | Data |
---|---|---|
28044bab JH |
1 | Git v1.6.5.4 Release Notes |
2 | ========================== | |
3 | ||
4 | Fixes since v1.6.5.3 | |
5 | -------------------- | |
6 | ||
7 | * "git help" (without argument) used to check if you are in a directory | |
8 | under git control. There was no breakage in behaviour per-se, but this | |
9 | was unnecessary. | |
10 | ||
11 | * "git prune-packed" gave progress output even when its standard error is | |
12 | not connected to a terminal; this caused cron jobs that run it to | |
031fd4b9 | 13 | produce cruft. |
28044bab JH |
14 | |
15 | * "git pack-objects --all-progress" is an option to ask progress output | |
16 | from write-object phase _if_ progress output were to be produced, and | |
17 | shouldn't have forced the progress output. | |
18 | ||
19 | * "git apply -p<n> --directory=<elsewhere>" did not work well for a | |
20 | non-default value of n. | |
21 | ||
22 | * "git merge foo HEAD" was misparsed as an old-style invocation of the | |
23 | command and produced a confusing error message. As it does not specify | |
24 | any other branch to merge, it shouldn't be mistaken as such. We will | |
25 | remove the old style "git merge <message> HEAD <commit>..." syntax in | |
26 | future versions, but not in this release, | |
27 | ||
28 | * "git merge -m <message> <branch>..." added the standard merge message | |
22e5e58a | 29 | on its own after user-supplied message, which should have overridden the |
28044bab JH |
30 | standard one. |
31 | ||
32 | Other minor documentation updates are included. |