tree-wide: fix some double word errors like "the the"

By chance (because I had this mistake in my own commit) I noticed
that there are a bunch of duplicated works like "the the" in the
code and man-pages.

This commit fixes them and some similar issues with "and and" etc.
This commit is contained in:
Michael Vogt
2026-07-09 13:09:52 +01:00
committed by Luca Boccassi
parent 944b160007
commit c944af8459
14 changed files with 14 additions and 14 deletions
+1 -1
View File
@@ -2628,7 +2628,7 @@ int setup_namespace(const NamespaceParameters *p, char **reterr_path) {
root_mount_fd = _root_mount_fd;
}
/* Try to to clone the directory mount if we have privs to, so that we can apply the
/* Try to clone the directory mount if we have privs to, so that we can apply the
* MS_SLAVE propagation settings right-away. */
if (root_mount_fd < 0) {
_root_mount_fd = open_tree_attr_with_fallback(
+1 -1
View File
@@ -15,7 +15,7 @@ typedef enum UnifiedSection {
UNIFIED_SECTION_DTB,
UNIFIED_SECTION_UNAME,
UNIFIED_SECTION_SBAT,
UNIFIED_SECTION_PCRSIG, /* This is is not measured actually */
UNIFIED_SECTION_PCRSIG, /* This is not measured actually */
UNIFIED_SECTION_PCRPKEY,
UNIFIED_SECTION_PROFILE,
UNIFIED_SECTION_DTBAUTO,
+1 -1
View File
@@ -23,7 +23,7 @@
* of resolution requests we keep multiple connections open thus, but not too many. */
#define HOOK_IDLE_CONNECTIONS_MAX 4U
/* Encapsulates a specific hook, i.e. bound socket in in the /run/systemd/resolve.hook/ directory */
/* Encapsulates a specific hook, i.e. bound socket in the /run/systemd/resolve.hook/ directory */
typedef struct Hook {
unsigned n_ref;
+1 -1
View File
@@ -456,7 +456,7 @@ static int mstack_load_now(MStack *mstack, const char *dir, int dir_fd, MStackFl
if (dir_fd < 0) {
_dir_fd = openat(AT_FDCWD, isempty(dir) ? "." : dir, O_DIRECTORY|O_CLOEXEC);
if (_dir_fd < 0)
return log_debug_errno(errno, "Failed to to open '%s': %m", dir);
return log_debug_errno(errno, "Failed to open '%s': %m", dir);
dir_fd = _dir_fd;
} else {
+1 -1
View File
@@ -26,7 +26,7 @@ SD_VARLINK_DEFINE_ENUM_TYPE(
SD_VARLINK_DEFINE_ENUM_VALUE(user_early_light),
SD_VARLINK_FIELD_COMMENT("Display manager greeter screen used for login"),
SD_VARLINK_DEFINE_ENUM_VALUE(greeter),
SD_VARLINK_FIELD_COMMENT("Similar, but a a lock screen"),
SD_VARLINK_FIELD_COMMENT("Similar, but a lock screen"),
SD_VARLINK_DEFINE_ENUM_VALUE(lock_screen),
SD_VARLINK_FIELD_COMMENT("Background session (that has no TTY, VT, Seat)"),
SD_VARLINK_DEFINE_ENUM_VALUE(background),
+1 -1
View File
@@ -39,7 +39,7 @@ static SD_VARLINK_DEFINE_METHOD(
ResolveRecord,
SD_VARLINK_FIELD_COMMENT("The question being looked up, i.e. a combination of resource record keys. Note that unlike DNS "
"queries on the wire these lookups can carry multiple key requests, albeit closely related ones. "
"Specifically, lookups for A+AAAA for the the same hostname are submitted as one question, as "
"Specifically, lookups for A+AAAA for the same hostname are submitted as one question, as "
"are lookups for TXT+SRV when doing DNS-SD resolution. Moreover, when looking up resources with "
"non-ASCII characters, they are placed together in a single question, once with labels encoded in "
"UTF-8, and once in IDNA. Hook implementations must be able to deal with these and other similar "
+1 -1
View File
@@ -187,7 +187,7 @@ static int find_gpt_root(UdevEvent *event, blkid_probe pr, const char *loop_back
* hence no need to bother with searching for ESP/XBOOTLDR */
need_esp_or_xbootldr = false;
} else
/* We now know the the ESP/xbootldr UUID, but we cannot be sure yet it's on this block
/* We now know the ESP/xbootldr UUID, but we cannot be sure yet it's on this block
* device, hence look for it among partitions now */
need_esp_or_xbootldr = true;
} else {