@@ -14,6 +14,11 @@ Fixes since v1.7.12
14
14
subcommands can be abbreviated to the unique prefix, but it was not
15
15
easy to find it described for new readers of the documentation set.
16
16
17
+ * The synopsis said "checkout [-B branch]" to make it clear the
18
+ branch name is a parameter to the option, but the heading for the
19
+ option description was "-B::", not "-B branch::", making the
20
+ documentation misleading.
21
+
17
22
* The "--topo-order", "--date-order" (and the lack of either means
18
23
the default order) options to "rev-list" and "log" family of
19
24
commands were poorly described in the documentation.
@@ -36,6 +41,14 @@ Fixes since v1.7.12
36
41
37
42
* Fallback 'getpass' implementation made unportable use of stdio API.
38
43
44
+ * "git apply -p0" did not parse pathnames on "diff --git" line
45
+ correctly. This caused patches that had pathnames in no other
46
+ places to be mistakenly rejected (most notably, binary patch that
47
+ does not rename nor change mode). Textual patches, renames or mode
48
+ changes have preimage and postimage pathnames in different places
49
+ in a form that can be parsed unambiguously and did not suffer from
50
+ this problem.
51
+
39
52
* "git commit --amend" let the user edit the log message and then
40
53
died when the human-readable committer name was given
41
54
insufficiently by getpwent(3).
@@ -44,9 +57,22 @@ Fixes since v1.7.12
44
57
did not advertise that they are available. fetch-pack has been
45
58
fixed not to do so.
46
59
60
+ * "git for-each-ref" did not currectly support more than one --sort
61
+ option.
62
+
63
+ * "git log .." errored out saying it is both rev range and a path
64
+ when there is no disambiguating "--" is on the command line.
65
+ Update the command line parser to interpret ".." as a path in such
66
+ a case.
67
+
47
68
* "git prune" without "-v" used to warn about leftover temporary
48
69
files (which is an indication of an earlier aborted operation).
49
70
71
+ * Pushing to smart HTTP server with recent Git fails without having
72
+ the username in the URL to force authentication, if the server is
73
+ configured to allow GET anonymously, while requiring authentication
74
+ for POST.
75
+
50
76
* The reflog entries left by "git rebase" and "git rebase -i" were
51
77
inconsistent (the interactive one gave an abbreviated object name).
52
78
0 commit comments