···431431 * but I observed ERROR_ACCESS_DENIED (0x05) errors during
432432 * testing.
433433 *
434434- * Note that we only get notificaiton events for events
434434+ * Note that we only get notification events for events
435435 * *within* the directory, not *on* the directory itself.
436436- * (These might be properies of the parent directory, for
436436+ * (These might be properties of the parent directory, for
437437 * example).
438438 *
439439 * NEEDSWORK: We might try to check for the deleted directory
+1-1
compat/regex/regexec.c
···292292 concerned.
293293294294 If REGS is not NULL, and BUFP->no_sub is not set, the offsets of the match
295295- and all groups is stroed in REGS. (For the "_2" variants, the offsets are
295295+ and all groups are stored in REGS. (For the "_2" variants, the offsets are
296296 computed relative to the concatenation, not relative to the individual
297297 strings.)
298298
+1-1
compat/simple-ipc/ipc-unix-socket.c
···713713 * Block SIGPIPE in this thread for the life of the thread. This
714714 * avoids any stray SIGPIPE signals when closing pipe fds under
715715 * extremely heavy loads (such as when the fifo queue is full and we
716716- * drop incomming connections).
716716+ * drop incoming connections).
717717 */
718718static void *accept_thread_proc(void *_accept_thread_data)
719719{
+2-2
contrib/completion/git-completion.bash
···32963296 # i.e. which are *already* part of their
32973297 # sparse-checkout. Thus, normal file and directory
32983298 # completion is always useless for "git
32993299- # sparse-checkout add" and is also probelmatic for
32993299+ # sparse-checkout add" and is also problematic for
33003300 # "git sparse-checkout set" unless using it to
33013301 # strictly narrow the checkout.
33023302 COMPREPLY=( "" )
···36983698 # Here we are not completing an --option, it's either the
36993699 # path or a ref.
37003700 case "$prev" in
37013701- -b|-B) # Complete refs for branch to be created/reseted.
37013701+ -b|-B) # Complete refs for branch to be created/reset.
37023702 __git_complete_refs
37033703 ;;
37043704 -*) # The previous word is an -o|--option without an
+1-1
contrib/subtree/git-subtree.sh
···946946 rev=$(git rev-parse -q --verify "$1^{commit}") ||
947947 die "fatal: '$1' does not refer to a commit"
948948 else
949949- die "fatal: you must provide exactly one revision, and optionnally a repository. Got: '$*'"
949949+ die "fatal: you must provide exactly one revision, and optionally a repository. Got: '$*'"
950950 fi
951951 repository=""
952952 if test "$#" = 2
+1-1
contrib/subtree/t/t7900-subtree.sh
···4747# pre-2.32.0 versions of 'git subtree' would write the hash of the tag
4848# (sub1 below), instead of the commit (sub1^{commit}) in the
4949# "git-subtree-split" trailer.
5050-# We immitate this behaviour below using a replace ref.
5050+# We imitate this behaviour below using a replace ref.
5151# This function creates 3 repositories:
5252# - $1
5353# - $1-sub (added as subtree "sub" in $1)
+1-1
t/helper/test-rot13-filter.c
···99 * ("clean", "smudge", etc).
1010 *
1111 * When --always-delay is given all pathnames with the "can-delay" flag
1212- * that don't appear on the list bellow are delayed with a count of 1
1212+ * that don't appear on the list below are delayed with a count of 1
1313 * (see more below).
1414 *
1515 * This implementation supports special test cases:
+1-1
t/lib-bundle.sh
···1111}
12121313# Check count of objects in a bundle file.
1414-# We can use "--thin" opiton to check thin pack, which must be fixed by
1414+# We can use "--thin" option to check thin pack, which must be fixed by
1515# command `git-index-pack --fix-thin --stdin`.
1616test_bundle_object_count () {
1717 thin=
+1-1
t/lib-rebase.sh
···187187 exit 1
188188 fi
189189 fi &&
190190- # There should be no uncommited changes
190190+ # There should be no uncommitted changes
191191 git diff --exit-code HEAD &&
192192 # The todo-list should be re-read after a reword
193193 GIT_SEQUENCE_EDITOR="\"$PWD/reword-sequence-editor.sh\"" \
+1-1
t/lib-sudo.sh
···66 local RUN="$TEST_DIRECTORY/$$.sh"
77 write_script "$RUN" "$TEST_SHELL_PATH"
88 # avoid calling "$RUN" directly so sudo doesn't get a chance to
99- # override the shell, add aditional restrictions or even reject
99+ # override the shell, add additional restrictions or even reject
1010 # running the script because its security policy deem it unsafe
1111 sudo "$TEST_SHELL_PATH" -c "\"$RUN\""
1212 ret=$?
+1-1
t/lib-unicode-nfc-nfd.sh
···7474# Yielding: \xcf \x89 + \xcc \x94 + \xcd \x82
7575#
7676# Note that I've used the canonical ordering of the
7777-# combinining characters. It is also possible to
7777+# combining characters. It is also possible to
7878# swap them. My testing shows that that non-standard
7979# ordering also causes a collision in mkdir. However,
8080# the resulting names don't draw correctly on the
+1-1
t/perf/p7527-builtin-fsmonitor.sh
···9595# time is not useful.
9696#
9797# Create a temp branch and do all work relative to it so that we don't
9898-# accidentially alter the real ballast branch.
9898+# accidentally alter the real ballast branch.
9999#
100100test_expect_success "Setup borrowed repo (temp ballast branch)" "
101101 test_might_fail git -C $REPO checkout $BALLAST_BR &&
+2-2
t/perf/perf-lib.sh
···282282# Run the performance test script specified in perf-test with
283283# optional prerequisite and setup steps.
284284# Options:
285285-# --prereq prerequisites: Skip the test if prequisites aren't met
285285+# --prereq prerequisites: Skip the test if prerequisites aren't met
286286# --setup "setup-steps": Run setup steps prior to each measured iteration
287287#
288288test_perf () {
···309309# prerequisites and setup steps. Returns the numeric value
310310# returned by size-test.
311311# Options:
312312-# --prereq prerequisites: Skip the test if prequisites aren't met
312312+# --prereq prerequisites: Skip the test if prerequisites aren't met
313313# --setup "setup-steps": Run setup steps prior to the size measurement
314314315315test_size () {
···459459 TEST(t_merged_logs(), "merged table with multiple log updates for same ref");
460460 TEST(t_merged_refs(), "merged table with multiple updates to same ref");
461461 TEST(t_merged_seek_multiple_times(), "merged table can seek multiple times");
462462- TEST(t_merged_single_record(), "ref ocurring in only one record can be fetched");
462462+ TEST(t_merged_single_record(), "ref occurring in only one record can be fetched");
463463464464 return test_done();
465465}