global: Fix duplicate word typos
Used regex to find these typos: (?<!struct )(?<=\s)([a-z]{1,}) \1(?=\s) Signed-off-by: Sven Strickroth <email@cs-ware.de> Signed-off-by: Taylor Blau <me@ttaylorr.com>
Sven Strickroth committed
Oct 21, 2024 at 17:12 UTC
c32d4a8cfe467f5cc5df70b87db27fa210d63d4b
11 files changed
+11
-11
Documentation/RelNotes/2.45.0.txt
+1
-1
@@ -9,7 +9,7 @@ UI, Workflows & Features
9
With "git init --ref-format=reftable", hopefully it would be a lot
10
more efficient to manage a repository with many references.
11
12
- * "git checkout -p" and friends learned that that "@" is a synonym
12
+ * "git checkout -p" and friends learned that "@" is a synonym
13
for "HEAD".
14
15
* Variants of vimdiff learned to honor mergetool.<variant>.layout
Documentation/RelNotes/2.46.0.txt
+1
-1
@@ -78,7 +78,7 @@ UI, Workflows & Features
78
turn on cover letters automatically (unless told never to enable
79
cover letter with "--no-cover-letter" and such).
80
81
- * The "--heads" option of "ls-remote" and "show-ref" has been been
81
+ * The "--heads" option of "ls-remote" and "show-ref" has been
82
deprecated; "--branches" replaces "--heads".
83
84
* For over a year, setting add.interactive.useBuiltin configuration
Documentation/git-format-patch.txt
+1
-1
@@ -250,7 +250,7 @@ is not complete yet ("WIP" stands for "Work In Progress").
250
+
251
If the convention of the receiving community for a particular extra
252
string is to have it _after_ the subject prefix, the string _<rfc>_
253
-can be prefixed with a dash ("`-`") to signal that the the rest of
253
+can be prefixed with a dash ("`-`") to signal that the rest of
254
the _<rfc>_ string should be appended to the subject prefix instead,
255
e.g., `--rfc='-(WIP)'` results in "PATCH (WIP)".
256
Documentation/gitprotocol-v2.txt
+1
-1
@@ -776,7 +776,7 @@ This would allow for optimizing the common case of servers who'd like
776
to provide one "big bundle" containing only their "main" branch,
777
and/or incremental updates thereof.
778
+
779
-A client receiving such a a response MAY assume that they can skip
779
+A client receiving such a response MAY assume that they can skip
780
retrieving the header from a bundle at the indicated URI, and thus
781
save themselves and the server(s) the request(s) needed to inspect the
782
headers of that bundle or bundles.
Documentation/howto/keep-canonical-history-correct.txt
+1
-1
@@ -13,7 +13,7 @@ that appears to be "backwards" from what other project developers
13
expect. This howto presents a suggested integration workflow for
14
maintaining a central repository.
15
16
-Suppose that that central repository has this history:
16
+Suppose that the central repository has this history:
17
18
------------
19
---o---o---A
builtin/difftool.c
+1
-1
@@ -340,7 +340,7 @@ static void write_file_in_directory(struct strbuf *dir, size_t dir_len,
340
/* Write the file contents for the left and right sides of the difftool
341
* dir-diff representation for submodules and symlinks. Symlinks and submodules
342
* are written as regular text files so that external diff tools can diff them
343
- * as text files, resulting in behavior that is analogous to to what "git diff"
343
+ * as text files, resulting in behavior that is analogous to what "git diff"
344
* displays for symlink and submodule diffs.
345
*/
346
static void write_standin_files(struct pair_entry *entry,
ci/lib.sh
+1
-1
@@ -62,7 +62,7 @@ trap "end_group 'CI setup'" EXIT
62
# something went wrong.
63
#
64
# We already enabled tracing executed commands earlier. This helps by showing
65
-# how # environment variables are set and and dependencies are installed.
65
+# how # environment variables are set and dependencies are installed.
66
set -e
67
68
skip_branch_tip_with_tag () {
fsmonitor.c
+1
-1
@@ -247,7 +247,7 @@ static size_t handle_using_name_hash_icase(
247
* technically this is a tracked file or a sparse-directory.
248
* It should not have any entries in the untracked-cache, so
249
* we should not need to use the case-corrected spelling to
250
- * invalidate the the untracked-cache. So we may not need to
250
+ * invalidate the untracked-cache. So we may not need to
251
* do this. For now, I'm going to be conservative and always
252
* do it; we can revisit this later.
253
*/
oidtree.c
+1
-1
@@ -47,7 +47,7 @@ void oidtree_insert(struct oidtree *ot, const struct object_id *oid)
47
48
/*
49
* n.b. Current callers won't get us duplicates, here. If a
50
- * future caller causes duplicates, there'll be a a small leak
50
+ * future caller causes duplicates, there'll be a small leak
51
* that won't be freed until oidtree_clear. Currently it's not
52
* worth maintaining a free list
53
*/
read-cache-ll.h
+1
-1
@@ -196,7 +196,7 @@ struct index_state {
196
*
197
* If the variable won't be used again, use release_index() to free()
198
* its resources. If it needs to be used again use discard_index(),
199
- * which does the same thing, but will use use index_state_init() at
199
+ * which does the same thing, but will use index_state_init() at
200
* the end. The discard_index() will use its own "istate->repo" as the
201
* "r" argument to index_state_init() in that case.
202
*/
refs/reftable-backend.c
+1
-1
@@ -2131,7 +2131,7 @@ static int write_reflog_existence_table(struct reftable_writer *writer,
2131
reftable_writer_set_limits(writer, ts, ts);
2132
2133
/*
2134
- * The existence entry has both old and new object ID set to the the
2134
+ * The existence entry has both old and new object ID set to the
2135
* null object ID. Our iterators are aware of this and will not present
2136
* them to their callers.
2137
*/