freshlybakedca.ke
Git fork
Update draft release notes to 1.7.10
Also apply typofixes people on the list helped spotting and
correcting.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
+28
-10
+28
-10
Documentation/RelNotes/1.7.10.txt
+28
-10
Documentation/RelNotes/1.7.10.txt
···
43
43
44
44
* A content filter (clean/smudge) used to be just a way to make the
45
45
recorded contents "more useful", and allowed to fail; a filter can
46
-
new optionally be marked as "required".
46
+
now optionally be marked as "required".
47
47
48
48
* Options whose names begin with "--no-" (e.g. the "--no-verify"
49
49
option of the "git commit" command) can be negated by omitting
50
50
"no-" from its name, e.g. "git commit --verify".
51
51
52
52
* "git am" learned to pass "-b" option to underlying "git mailinfo", so
53
-
that bracketed string other than "PATCH" at the beginning can be kept.
53
+
that a bracketed string other than "PATCH" at the beginning can be kept.
54
54
55
55
* "git clone" learned "--single-branch" option to limit cloning to a
56
-
single branch (surprise!).
56
+
single branch (surprise!); tags that do not point into the history
57
+
of the branch are not fetched.
57
58
58
59
* "git clone" learned to detach the HEAD in the resulting repository
59
-
when the source repository's HEAD does not point to a branch.
60
+
when the user specifies a tag with "--branch" (e.g., "--branch=v1.0").
61
+
Clone also learned to print the usual "detached HEAD" advice in such
62
+
a case, similar to "git checkout v1.0".
60
63
61
64
* When showing a patch while ignoring whitespace changes, the context
62
65
lines are taken from the postimage, in order to make it easier to
···
71
74
* "fsck" learned "--no-dangling" option to omit dangling object
72
75
information.
73
76
74
-
* "git log -G" learned to pay attention to the "-i" option and can
75
-
find patch hunks that introduce or remove a string that matches the
76
-
given pattern ignoring the case.
77
+
* "git log -G" and "git log -S" learned to pay attention to the "-i"
78
+
option. With "-i", "log -G" ignores the case when finding patch
79
+
hunks that introduce or remove a string that matches the given
80
+
pattern. Similarly with "-i", "log -S" ignores the case when
81
+
finding the commit the given block of text appears or disappears
82
+
from the file.
77
83
78
84
* "git merge" in an interactive session learned to spawn the editor
79
85
by default to let the user edit the auto-generated merge message,
···
82
88
Both "git merge" and "git pull" can be given --no-edit from the
83
89
command line to accept the auto-generated merge message.
84
90
85
-
* The advise message given when the user didn't give enough clue on
91
+
* The advice message given when the user didn't give enough clue on
86
92
what to merge to "git pull" and "git merge" has been updated to
87
93
be more concise and easier to understand.
88
94
89
95
* "git push" learned the "--prune" option, similar to "git fetch".
90
96
97
+
* The whole directory that houses a top-level superproject managed by
98
+
"git submodule" can be moved to another place.
99
+
91
100
* "git symbolic-ref" learned the "--short" option to abbreviate the
92
101
refname it shows unambiguously.
93
102
···
95
104
output to those that point at the given object.
96
105
97
106
* "gitweb" allows intermediate entries in the directory hierarchy
98
-
that leads to a projects to be clicked, which in turn shows the
107
+
that leads to a project to be clicked, which in turn shows the
99
108
list of projects inside that directory.
100
109
101
110
* "gitweb" learned to read various pieces of information for the
···
149
158
* The code to check if a path points at a file beyond a symbolic link
150
159
has been restructured to be thread-safe.
151
160
161
+
* When pruning directories that has become empty during "git prune"
162
+
and "git prune-packed", call closedir() that iterates over a
163
+
directory before rmdir() it.
164
+
152
165
Also contains minor documentation updates and code clean-ups.
153
166
154
167
···
179
192
accessed in a repository whose HEAD does not point at a valid
180
193
branch.
181
194
195
+
* "gitweb" did use quotemeta() to prepare search string when asked to
196
+
do a fixed-string project search, but did not use it by mistake and
197
+
used the user-supplied string instead.
198
+
(merge e65ceb6 jn/maint-do-not-match-with-unsanitized-searchtext later to maint).
199
+
182
200
---
183
201
exec >/var/tmp/1
184
-
O=v1.7.9.3-366-g1e4d087
202
+
O=v1.7.10-rc0-15-g9a4c97e
185
203
echo O=$(git describe)
186
204
git log --first-parent --oneline ^maint $O..
187
205
echo