@@ -34,7 +34,7 @@ UI, Workflows & Features
34
34
have a place to store the updated notes tree, iow, a ref).
35
35
36
36
* "git grep" by default does not fall back to its "--no-index"
37
- behaviour outside a directory under Git's control (otherwise the
37
+ behavior outside a directory under Git's control (otherwise the
38
38
user may by mistake end up running a huge recursive search); with a
39
39
new configuration (set in $HOME/.gitconfig--by definition this
40
40
cannot be set in the config file per project), this safety can be
@@ -55,7 +55,7 @@ UI, Workflows & Features
55
55
56
56
* Many commands that read files that are expected to contain text
57
57
that is generated (or can be edited) by the end user to control
58
- their behaviour (e.g. "git grep -f <filename>") have been updated
58
+ their behavior (e.g. "git grep -f <filename>") have been updated
59
59
to be more tolerant to lines that are terminated with CRLF (they
60
60
used to treat such a line to contain payload that ends with CR,
61
61
which is usually not what the users expect).
@@ -187,7 +187,7 @@ Performance, Internal Implementation, Development Support etc.
187
187
with expectations that are not satisfiable on Git for Windows.
188
188
189
189
* Some calls to strcpy(3) triggers a false warning from static
190
- analysers that are less intelligent than humans, and reducing the
190
+ analyzers that are less intelligent than humans, and reducing the
191
191
number of these false hits helps us notice real issues. A few
192
192
calls to strcpy(3) in a couple of protrams that are already safe
193
193
has been rewritten to avoid false warnings.
@@ -281,7 +281,7 @@ notes for details).
281
281
* "git send-email" was confused by escaped quotes stored in the alias
282
282
files saved by "mutt", which has been corrected.
283
283
284
- * A few unportable C construct have been spotted by clang compiler
284
+ * A few non-portable C construct have been spotted by clang compiler
285
285
and have been fixed.
286
286
287
287
* The documentation has been updated to hint the connection between
@@ -349,10 +349,10 @@ notes for details).
349
349
* "git worktree" had a broken code that attempted to auto-fix
350
350
possible inconsistency that results from end-users moving a
351
351
worktree to different places without telling Git (the original
352
- repository needs to maintain backpointers to its worktrees, but
353
- "mv" run by end-users who are not familiar with that fact will
354
- obviously not adjust them), which actually made things worse
355
- when triggered.
352
+ repository needs to maintain back-pointers to its worktrees,
353
+ but "mv" run by end-users who are not familiar with that fact
354
+ will obviously not adjust them), which actually made things
355
+ worse when triggered.
356
356
357
357
* The low-level merge machinery has been taught to use CRLF line
358
358
termination when inserting conflict markers to merged contents that
0 commit comments