Git fork

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>

authored by

Sven Strickroth and committed by
Taylor Blau
c32d4a8c 34b6ce9b

+11 -11
+1 -1
Documentation/RelNotes/2.45.0.txt
··· 9 9 With "git init --ref-format=reftable", hopefully it would be a lot 10 10 more efficient to manage a repository with many references. 11 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 13 for "HEAD". 14 14 15 15 * Variants of vimdiff learned to honor mergetool.<variant>.layout
+1 -1
Documentation/RelNotes/2.46.0.txt
··· 78 78 turn on cover letters automatically (unless told never to enable 79 79 cover letter with "--no-cover-letter" and such). 80 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 82 deprecated; "--branches" replaces "--heads". 83 83 84 84 * For over a year, setting add.interactive.useBuiltin configuration
+1 -1
Documentation/git-format-patch.txt
··· 250 250 + 251 251 If the convention of the receiving community for a particular extra 252 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 254 the _<rfc>_ string should be appended to the subject prefix instead, 255 255 e.g., `--rfc='-(WIP)'` results in "PATCH (WIP)". 256 256
+1 -1
Documentation/gitprotocol-v2.txt
··· 776 776 to provide one "big bundle" containing only their "main" branch, 777 777 and/or incremental updates thereof. 778 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 780 retrieving the header from a bundle at the indicated URI, and thus 781 781 save themselves and the server(s) the request(s) needed to inspect the 782 782 headers of that bundle or bundles.
+1 -1
Documentation/howto/keep-canonical-history-correct.txt
··· 13 13 expect. This howto presents a suggested integration workflow for 14 14 maintaining a central repository. 15 15 16 - Suppose that that central repository has this history: 16 + Suppose that the central repository has this history: 17 17 18 18 ------------ 19 19 ---o---o---A
+1 -1
builtin/difftool.c
··· 340 340 /* Write the file contents for the left and right sides of the difftool 341 341 * dir-diff representation for submodules and symlinks. Symlinks and submodules 342 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 344 * displays for symlink and submodule diffs. 345 345 */ 346 346 static void write_standin_files(struct pair_entry *entry,
+1 -1
ci/lib.sh
··· 62 62 # something went wrong. 63 63 # 64 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 66 set -e 67 67 68 68 skip_branch_tip_with_tag () {
+1 -1
fsmonitor.c
··· 247 247 * technically this is a tracked file or a sparse-directory. 248 248 * It should not have any entries in the untracked-cache, so 249 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 251 * do this. For now, I'm going to be conservative and always 252 252 * do it; we can revisit this later. 253 253 */
+1 -1
oidtree.c
··· 47 47 48 48 /* 49 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 51 * that won't be freed until oidtree_clear. Currently it's not 52 52 * worth maintaining a free list 53 53 */
+1 -1
read-cache-ll.h
··· 196 196 * 197 197 * If the variable won't be used again, use release_index() to free() 198 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 200 * the end. The discard_index() will use its own "istate->repo" as the 201 201 * "r" argument to index_state_init() in that case. 202 202 */
+1 -1
refs/reftable-backend.c
··· 2131 2131 reftable_writer_set_limits(writer, ts, ts); 2132 2132 2133 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 2135 * null object ID. Our iterators are aware of this and will not present 2136 2136 * them to their callers. 2137 2137 */