@@ -7,19 +7,19 @@ Backward compatibility notes
7
7
"git submodule foreach $cmd $args" used to treat "$cmd $args" the same
8
8
way "ssh" did, concatenating them into a single string and letting the
9
9
shell unquote. Careless users who forget to sufficiently quote $args
10
- gets their argument split at $IFS whitespaces by the shell, and got
10
+ get their argument split at $IFS whitespaces by the shell, and got
11
11
unexpected results due to this. Starting from this release, the
12
12
command line is passed directly to the shell, if it has an argument.
13
13
14
14
Read-only support for experimental loose-object format, in which users
15
- could optionally choose to write in their loose objects for a short
16
- while between v1.4.3 to v1.5.3 era, has been dropped.
15
+ could optionally choose to write their loose objects for a short
16
+ while between v1.4.3 and v1.5.3 era, has been dropped.
17
17
18
- The meanings of "--tags" option to "git fetch" has changed; the
19
- command fetches tags _in addition to_ what are fetched by the same
18
+ The meanings of the "--tags" option to "git fetch" has changed; the
19
+ command fetches tags _in addition to_ what is fetched by the same
20
20
command line without the option.
21
21
22
- The way "git push $there $what" interprets $what part given on the
22
+ The way "git push $there $what" interprets the $what part given on the
23
23
command line, when it does not have a colon that explicitly tells us
24
24
what ref at the $there repository is to be updated, has been enhanced.
25
25
@@ -96,7 +96,7 @@ UI, Workflows & Features
96
96
primarily because the codepaths involved were not carefully vetted
97
97
and we did not bother supporting such usage. This release attempts
98
98
to allow object transfer out of a shallowly-cloned repository in a
99
- more controlled way (i.e. the receiver become a shallow repository
99
+ more controlled way (i.e. the receiver becomes a shallow repository
100
100
with a truncated history).
101
101
102
102
* Just like we give a reasonable default for "less" via the LESS
@@ -107,12 +107,12 @@ UI, Workflows & Features
107
107
hierarchies, whose variables are predominantly three-level, were
108
108
not completed by hitting a <TAB> in bash and zsh completions.
109
109
110
- * Fetching 'frotz' branch with "git fetch", while 'frotz/nitfol'
110
+ * Fetching a 'frotz' branch with "git fetch", while a 'frotz/nitfol'
111
111
remote-tracking branch from an earlier fetch was still there, would
112
112
error out, primarily because the command was not told that it is
113
113
allowed to lose any information on our side. "git fetch --prune"
114
- now can be used to remove 'frotz/nitfol' to make room to fetch and
115
- store 'frotz' remote-tracking branch.
114
+ now can be used to remove 'frotz/nitfol' to make room for fetching and
115
+ storing the 'frotz' remote-tracking branch.
116
116
117
117
* "diff.orderfile=<file>" configuration variable can be used to
118
118
pretend as if the "-O<file>" option were given from the command
@@ -218,7 +218,7 @@ track are contained in this release (see the maintenance releases' notes
218
218
for details).
219
219
220
220
* The pathspec matching code, while comparing two trees (e.g. "git
221
- diff A B -- path1 path2") was too agrresive and failed to match
221
+ diff A B -- path1 path2") was too aggressive and failed to match
222
222
some paths when multiple pathspecs were involved.
223
223
(merge e4ddb05 as/tree-walk-fix-aggressive-short-cut later to maint).
224
224
@@ -227,11 +227,11 @@ for details).
227
227
(merge b861e23 sb/repack-in-c later to maint).
228
228
229
229
* An earlier update in v1.8.4.x to "git rev-list --objects" with
230
- negative ref had performance regression.
230
+ negative ref had a performance regression.
231
231
(merge 200abe7 jk/mark-edges-uninteresting later to maint).
232
232
233
233
* A recent update to "git send-email" broke platforms where
234
- /etc/ssl/certs/ directory exists, but it cannot used as SSL_ca_path
234
+ /etc/ssl/certs/ directory exists but cannot be used as SSL_ca_path
235
235
(e.g. Fedora rawhide).
236
236
(merge 01645b7 rk/send-email-ssl-cert later to maint).
237
237
@@ -275,8 +275,8 @@ for details).
275
275
names.
276
276
(merge 82246b7 nd/daemon-informative-errors-typofix later to maint).
277
277
278
- * There is no reason to have a hardcoded upper limit of the number of
279
- parents for an octopus merge, created via the graft mechanism, but
278
+ * There is no reason to have a hardcoded upper limit for the number of
279
+ parents of an octopus merge, created via the graft mechanism, but
280
280
there was.
281
281
(merge e228c17 js/lift-parent-count-limit later to maint).
282
282
@@ -306,8 +306,8 @@ for details).
306
306
* When we figure out how many file descriptors to allocate for
307
307
keeping packfiles open, a system with non-working getrlimit() could
308
308
cause us to die(), but because we make this call only to get a
309
- rough estimate of how many is available and we do not even attempt
310
- to use up all file descriptors available ourselves, it is nicer to
309
+ rough estimate of how many are available and we do not even attempt
310
+ to use up all available file descriptors ourselves, it is nicer to
311
311
fall back to a reasonable low value rather than dying.
312
312
(merge 491a8de jh/rlimit-nofile-fallback later to maint).
313
313
@@ -349,7 +349,7 @@ for details).
349
349
Diagnose it as an error.
350
350
(merge 5594bca nd/transport-positive-depth-only later to maint).
351
351
352
- * Remote repository URL expressed in scp-style host:path notation are
352
+ * Remote repository URLs expressed in scp-style host:path notation are
353
353
parsed more carefully (e.g. "foo/bar:baz" is local, "[::1]:/~user" asks
354
354
to connect to user's home directory on host at address ::1.
355
355
(merge a2036d7 tb/clone-ssh-with-colon-for-port later to maint).
0 commit comments