{"thread":{"id":"34558","subject":"[PATCH] More typofixes.","startedAt":"2013-07-29T08:18:21Z","lastAt":"2013-07-29T19:32:05Z","messageCount":11,"participants":["Ondřej Bílka","Bryan Turner","David Aguilar","Ramkumar Ramachandra","Marc Branchaud","Junio C Hamano","Stefan Beller"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"224213","messageId":"20130729081821.GA6758@domone.kolej.mff.cuni.cz","threadId":"34558","inReplyTo":null,"subject":"[PATCH] More typofixes.","fromName":"Ondřej Bílka","fromEmail":"neleai@seznam.cz","sentAt":"2013-07-29T08:18:21Z","receivedAt":"2013-07-29T08:18:21Z","isPatch":true,"sender":{"key":"neleai@seznam.cz","avatar":"https://avatars.githubusercontent.com/u/48067?v=4"},"body":"Hi,\n\nI improved my tool and it catched following additional typos.\n\nAs with any big project best way to catch errors is to have automated\nchecks that catch them ( Other possibility would be to read everything ten\ntimes to get error rate down but nobody wants to do it).\n\nIf you want you could add a pre-commit hook \nstylepp-spellcheck --hook\nthat checks comments for likely typos (misspells by aspell and not\noccurring in code). It uses aspell to identify them so you need to \nteach aspell which words are valid. \n\nI would like make possible to share dictionaries so teaching phase can\nbe done only once instead for each person but I did not found suitable\nworkflow yet.\n\n\nSigned-off-by: Ondřej Bílka <neleai@seznam.cz>\n\ndiff --git a/pathspec.c b/pathspec.c\nindex 6ea0867..27ffe77 100644\n--- a/pathspec.c\n+++ b/pathspec.c\n@@ -40,7 +40,7 @@ void add_pathspec_matches_against_index(const char **pathspec,\n /*\n  * Finds which of the given pathspecs match items in the index.\n  *\n- * This is a one-shot wrapper around add_pathspec_matches_against_index()\n+ * This is an one-shot wrapper around add_pathspec_matches_against_index()\n  * which allocates, populates, and returns a seen[] array indicating the\n  * nature of the \"closest\" (i.e. most specific) matches which each of the\n  * given pathspecs achieves against all items in the index.\ndiff --git a/builtin/log.c b/builtin/log.c\nindex 2625f98..01b49b3 100644\n--- a/builtin/log.c\n+++ b/builtin/log.c\n@@ -304,7 +304,7 @@ static void setup_early_output(struct rev_info *rev)\n \t * tenth of a second, don't even bother doing the\n \t * early-output thing..\n \t *\n-\t * This is a one-time-only trigger.\n+\t * This is an one-time-only trigger.\n \t */\n \tearly_output_timer.it_value.tv_sec = 0;\n \tearly_output_timer.it_value.tv_usec = 100000;\ndiff --git a/transport-helper.c b/transport-helper.c\nindex 45a35df..63cabc3 100644\n--- a/transport-helper.c\n+++ b/transport-helper.c\n@@ -1132,7 +1132,7 @@ static void *udt_copy_task_routine(void *udt)\n #ifndef NO_PTHREADS\n \n /*\n- * Join thread, with apporiate errors on failure. Name is name for the\n+ * Join thread, with appropriate errors on failure. Name is name for the\n  * thread (for error messages). Returns 0 on success, 1 on failure.\n  */\n static int tloop_join(pthread_t thread, const char *name)\ndiff --git a/transport-helper.c b/transport-helper.c\nindex 45a35df..63cabc3 100644\n--- a/transport-helper.c\n+++ b/transport-helper.c\n@@ -1198,7 +1198,7 @@ static void udt_kill_transfer(struct unidirectional_transfer *t)\n }\n \n /*\n- * Join process, with apporiate errors on failure. Name is name for the\n+ * Join process, with appropriate errors on failure. Name is name for the\n  * process (for error messages). Returns 0 on success, 1 on failure.\n  */\n static int tloop_join(pid_t pid, const char *name)\ndiff --git a/Documentation/RelNotes/1.7.11.7.txt b/Documentation/RelNotes/1.7.11.7.txt\nindex e7e79d9..e743a2a 100644\n--- a/Documentation/RelNotes/1.7.11.7.txt\n+++ b/Documentation/RelNotes/1.7.11.7.txt\n@@ -25,7 +25,7 @@ Fixes since v1.7.11.6\n    references\" nor \"Reload\" did not update what is shown as the\n    contents of it, when the user overwrote the tag with \"git tag -f\".\n \n- * \"git for-each-ref\" did not currectly support more than one --sort\n+ * \"git for-each-ref\" did not correctly support more than one --sort\n    option.\n \n  * \"git log ..\" errored out saying it is both rev range and a path\ndiff --git a/t/t9112-git-svn-md5less-file.sh b/t/t9112-git-svn-md5less-file.sh\nindex a61d671..9861c71 100755\n--- a/t/t9112-git-svn-md5less-file.sh\n+++ b/t/t9112-git-svn-md5less-file.sh\n@@ -7,7 +7,7 @@ test_description='test that git handles an svn repository with missing md5sums'\n # Loading a node from a svn dumpfile without a Text-Content-Length\n # field causes svn to neglect to store or report an md5sum.  (it will\n # calculate one if you had put Text-Content-Length: 0).  This showed\n-# up in a repository creted with cvs2svn.\n+# up in a repository created with cvs2svn.\n \n cat > dumpfile.svn <<EOF\n SVN-fs-dump-format-version: 1\ndiff --git a/read-cache.c b/read-cache.c\nindex d4474ea..c3d5e35 100644\n--- a/read-cache.c\n+++ b/read-cache.c\n@@ -489,7 +489,7 @@ int remove_index_entry_at(struct index_state *istate, int pos)\n }\n \n /*\n- * Remove all cache ententries marked for removal, that is where\n+ * Remove all cache entries marked for removal, that is where\n  * CE_REMOVE is set in ce_flags.  This is much more effective than\n  * calling remove_index_entry_at() for each entry to be removed.\n  */\ndiff --git a/t/t9020-remote-svn.sh b/t/t9020-remote-svn.sh\nindex d9f6b73..4d81ba1 100755\n--- a/t/t9020-remote-svn.sh\n+++ b/t/t9020-remote-svn.sh\n@@ -24,7 +24,7 @@ init_git () {\n \trm -fr .git &&\n \tgit init &&\n \t#git remote add svnsim testsvn::sim:///$TEST_DIRECTORY/t9020/example.svnrdump\n-\t# let's reuse an exisiting dump file!?\n+\t# let's reuse an existing dump file!?\n \tgit remote add svnsim testsvn::sim://$TEST_DIRECTORY/t9154/svn.dump\n \tgit remote add svnfile testsvn::file://$TEST_DIRECTORY/t9154/svn.dump\n }\ndiff --git a/builtin/push.c b/builtin/push.c\nindex 6d36c24..04f0eaf 100644\n--- a/builtin/push.c\n+++ b/builtin/push.c\n@@ -92,7 +92,7 @@ static NORETURN int die_push_simple(struct branch *branch, struct remote *remote\n \tif (!short_upstream)\n \t\tshort_upstream = branch->merge[0]->src;\n \t/*\n-\t * Don't show advice for people who explicitely set\n+\t * Don't show advice for people who explicitly set\n \t * push.default.\n \t */\n \tif (push_default == PUSH_DEFAULT_UNSPECIFIED)\ndiff --git a/Documentation/howto/new-command.txt b/Documentation/howto/new-command.txt\nindex 2abc3a0..d7de5a3 100644\n--- a/Documentation/howto/new-command.txt\n+++ b/Documentation/howto/new-command.txt\n@@ -94,7 +94,7 @@ your language, document it in the INSTALL file.\n 6. There is a file command-list.txt in the distribution main directory\n that categorizes commands by type, so they can be listed in appropriate\n subsections in the documentation's summary command list.  Add an entry\n-for yours.  To understand the categories, look at git-cmmands.txt\n+for yours.  To understand the categories, look at git-commands.txt\n in the main directory.\n \n 7. Give the maintainer one paragraph to include in the RelNotes file\ndiff --git a/t/lib-t6000.sh b/t/lib-t6000.sh\nindex 4ffd901..97c6ace 100644\n--- a/t/lib-t6000.sh\n+++ b/t/lib-t6000.sh\n@@ -34,7 +34,7 @@ save_tag () {\n \tmv sed.script.tmp sed.script\n }\n \n-# Replace unhelpful sha1 hashses with their symbolic equivalents\n+# Replace unhelpful sha1 hashes with their symbolic equivalents\n entag () {\n \tsed -f sed.script\n }\ndiff --git a/builtin/fast-export.c b/builtin/fast-export.c\nindex d1d68e9..8e19058 100644\n--- a/builtin/fast-export.c\n+++ b/builtin/fast-export.c\n@@ -379,7 +379,7 @@ static void handle_tag(const char *name, struct tag *tag)\n \tint tagged_mark;\n \tstruct commit *p;\n \n-\t/* Trees have no identifer in fast-export output, thus we have no way\n+\t/* Trees have no identifier in fast-export output, thus we have no way\n \t * to output tags of trees, tags of tags of trees, etc.  Simply omit\n \t * such tags.\n \t */\ndiff --git a/contrib/subtree/git-subtree.txt b/contrib/subtree/git-subtree.txt\nindex 7ba853e..e0957ee 100644\n--- a/contrib/subtree/git-subtree.txt\n+++ b/contrib/subtree/git-subtree.txt\n@@ -270,7 +270,7 @@ git-extensions repository in ~/git-extensions/:\n name\n \n You can omit the --squash flag, but doing so will increase the number\n-of commits that are incldued in your local repository.\n+of commits that are included in your local repository.\n \n We now have a ~/git-extensions/git-subtree directory containing code\n from the master branch of git://github.com/apenwarr/git-subtree.git\ndiff --git a/commit-slab.h b/commit-slab.h\nindex 7d48163..4f1c796 100644\n--- a/commit-slab.h\n+++ b/commit-slab.h\n@@ -22,7 +22,7 @@\n  *\n  *   Initializes the indegree slab that associates an array of integers\n  *   to each commit. 'stride' specifies how big each array is.  The slab\n- *   that id initialied by the variant without \"_with_stride\" associates\n+ *   that id initialized by the variant without \"_with_stride\" associates\n  *   each commit with an array of one integer.\n  */\n \ndiff --git a/t/gitweb-lib.sh b/t/gitweb-lib.sh\nindex ae2dc46..9e381e0 100644\n--- a/t/gitweb-lib.sh\n+++ b/t/gitweb-lib.sh\n@@ -36,7 +36,7 @@ EOF\n \n \t# You can set the GITWEB_TEST_INSTALLED environment variable to\n \t# the gitwebdir (the directory where gitweb is installed / deployed to)\n-\t# of an existing gitweb instalation to test that installation,\n+\t# of an existing gitweb installation to test that installation,\n \t# or simply to pathname of installed gitweb script.\n \tif test -n \"$GITWEB_TEST_INSTALLED\" ; then\n \t\tif test -d $GITWEB_TEST_INSTALLED; then\ndiff --git a/Documentation/RelNotes/1.7.9.1.txt b/Documentation/RelNotes/1.7.9.1.txt\nindex 6957183..e8fddb8 100644\n--- a/Documentation/RelNotes/1.7.9.1.txt\n+++ b/Documentation/RelNotes/1.7.9.1.txt\n@@ -20,7 +20,7 @@ Fixes since v1.7.9\n    submodule that only has uncommitted local changes in the patch\n    prepared by for the user to edit.\n \n- * Typo in \"git branch --edit-description my-tpoic\" was not diagnosed.\n+ * Typo in \"git branch --edit-description my-topic\" was not diagnosed.\n \n  * Using \"git grep -l/-L\" together with options -W or --break may not\n    make much sense as the output is to only count the number of hits\ndiff --git a/contrib/ciabot/ciabot.py b/contrib/ciabot/ciabot.py\nindex 36b5665..befa0c3 100755\n--- a/contrib/ciabot/ciabot.py\n+++ b/contrib/ciabot/ciabot.py\n@@ -70,7 +70,7 @@ tinyifier = \"http://tinyurl.com/api-create.php?url=\"\n \n # The template used to generate the XML messages to CIA.  You can make\n # visible changes to the IRC-bot notification lines by hacking this.\n-# The default will produce a notfication line that looks like this:\n+# The default will produce a notification line that looks like this:\n #\n # ${project}: ${author} ${repo}:${branch} * ${rev} ${files}: ${logmsg} ${url}\n #\ndiff --git a/contrib/ciabot/ciabot.sh b/contrib/ciabot/ciabot.sh\nindex 3fbbc53..dfb71a1 100755\n--- a/contrib/ciabot/ciabot.sh\n+++ b/contrib/ciabot/ciabot.sh\n@@ -39,7 +39,7 @@\n #       done\n #\n # The reason for the tac call is that git rev-list emits commits from\n-# most recent to least - better to ship notifactions from oldest to newest.\n+# most recent to least - better to ship notifications from oldest to newest.\n #\n # Configuration variables affecting this script:\n #\ndiff --git a/t/lib-t6000.sh b/t/lib-t6000.sh\nindex 4ffd901..97c6ace 100644\n--- a/t/lib-t6000.sh\n+++ b/t/lib-t6000.sh\n@@ -65,7 +65,7 @@ commit_date () {\n }\n \n # Assign the value of fake date to a variable, but\n-# allow fairly common \"1971-08-16 00:00\" to be omittd\n+# allow fairly common \"1971-08-16 00:00\" to be omitted\n assign_fake_date () {\n \tcase \"$2\" in\n \t??:??:??)\teval \"$1='1971-08-16 $2'\" ;;\ndiff --git a/read-cache.c b/read-cache.c\nindex d4474ea..c3d5e35 100644\n--- a/read-cache.c\n+++ b/read-cache.c\n@@ -1760,7 +1760,7 @@ static int has_racy_timestamp(struct index_state *istate)\n }\n \n /*\n- * Opportunisticly update the index but do not complain if we can't\n+ * Opportunistically update the index but do not complain if we can't\n  */\n void update_index_if_able(struct index_state *istate, struct lock_file *lockfile)\n {\ndiff --git a/git-mergetool--lib.sh b/git-mergetool--lib.sh\nindex 6a72106..feee6a4 100644\n--- a/git-mergetool--lib.sh\n+++ b/git-mergetool--lib.sh\n@@ -144,7 +144,7 @@ setup_user_tool () {\n setup_tool () {\n \ttool=\"$1\"\n \n-\t# Fallback definitions, to be overriden by tools.\n+\t# Fallback definitions, to be overridden by tools.\n \tcan_merge () {\n \t\treturn 0\n \t}\ndiff --git a/Documentation/RelNotes/1.7.10.4.txt b/Documentation/RelNotes/1.7.10.4.txt\nindex 326670d..57597f2 100644\n--- a/Documentation/RelNotes/1.7.10.4.txt\n+++ b/Documentation/RelNotes/1.7.10.4.txt\n@@ -7,7 +7,7 @@ Fixes since v1.7.10.3\n  * The message file for Swedish translation has been updated a bit.\n \n  * A name taken from mailmap was copied into an internal buffer\n-   incorrectly and could overun the buffer if it is too long.\n+   incorrectly and could overrun the buffer if it is too long.\n \n  * A malformed commit object that has a header line chomped in the\n    middle could kill git with a NULL pointer dereference.\ndiff --git a/git-p4.py b/git-p4.py\nindex 88fcf23..31e71ff 100755\n--- a/git-p4.py\n+++ b/git-p4.py\n@@ -1786,7 +1786,7 @@ class P4Submit(Command, P4UserMap):\n             missingGitTags = gitTags - p4Labels\n             self.exportGitTags(missingGitTags)\n \n-        # exit with error unless everything applied perfecly\n+        # exit with error unless everything applied perfectly\n         if len(commits) != len(applied):\n                 sys.exit(1)\n \ndiff --git a/combine-diff.c b/combine-diff.c\nindex 6dc0609..88525b3 100644\n--- a/combine-diff.c\n+++ b/combine-diff.c\n@@ -165,7 +165,7 @@ static struct lline *coalesce_lines(struct lline *base, int *lenbase,\n \n \t/*\n \t * Coalesce new lines into base by finding the LCS\n-\t * - Create the table to run dynamic programing\n+\t * - Create the table to run dynamic programming\n \t * - Compute the LCS\n \t * - Then reverse read the direction structure:\n \t *   - If we have MATCH, assign parent to base flag, and consume\ndiff --git a/t/t9802-git-p4-filetype.sh b/t/t9802-git-p4-filetype.sh\nindex b0d1d94..1962d3a 100755\n--- a/t/t9802-git-p4-filetype.sh\n+++ b/t/t9802-git-p4-filetype.sh\n@@ -28,7 +28,7 @@ test_expect_success 'p4 client newlines, unix' '\n \t\ttest_cmp f-unix-orig f-unix &&\n \n \t\t# make sure stored in repo as unix newlines\n-\t\t# use sed to eat python-appened newline\n+\t\t# use sed to eat python-appended newline\n \t\tp4 -G print //depot/f-unix | marshal_dump data 2 |\\\n \t\t    sed \\$d >f-unix-p4-print &&\n \t\ttest_cmp f-unix-orig f-unix-p4-print &&\ndiff --git a/t/t9802-git-p4-filetype.sh b/t/t9802-git-p4-filetype.sh\nindex b0d1d94..1962d3a 100755\n--- a/t/t9802-git-p4-filetype.sh\n+++ b/t/t9802-git-p4-filetype.sh\n@@ -55,7 +55,7 @@ test_expect_success 'p4 client newlines, win' '\n \t\ttest_cmp f-win-orig f-win &&\n \n \t\t# make sure stored in repo as unix newlines\n-\t\t# use sed to eat python-appened newline\n+\t\t# use sed to eat python-appended newline\n \t\tp4 -G print //depot/f-win | marshal_dump data 2 |\\\n \t\t    sed \\$d >f-win-p4-print &&\n \t\ttest_cmp f-win-as-lf f-win-p4-print &&\ndiff --git a/notes.h b/notes.h\nindex 3324c48..2a3f923 100644\n--- a/notes.h\n+++ b/notes.h\n@@ -77,7 +77,7 @@ const char *default_notes_ref(void);\n  * variable is used, and if that is missing, the default notes ref is used\n  * (\"refs/notes/commits\").\n  *\n- * If you need to re-intialize a notes_tree structure (e.g. when switching from\n+ * If you need to re-initialize a notes_tree structure (e.g. when switching from\n  * one notes ref to another), you must first de-initialize the notes_tree\n  * structure by calling free_notes(struct notes_tree *).\n  *\ndiff --git a/t/t7601-merge-pull-config.sh b/t/t7601-merge-pull-config.sh\nindex 25dac79..830a4c3 100755\n--- a/t/t7601-merge-pull-config.sh\n+++ b/t/t7601-merge-pull-config.sh\n@@ -109,7 +109,7 @@ test_expect_success 'setup conflicted merge' '\n '\n \n # First do the merge with resolve and recursive then verify that\n-# recusive is chosen.\n+# recursive is chosen.\n \n test_expect_success 'merge picks up the best result' '\n \tgit config --unset-all pull.twohead &&\ndiff --git a/cache.h b/cache.h\nindex 3a69638..85b544f 100644\n--- a/cache.h\n+++ b/cache.h\n@@ -491,7 +491,7 @@ extern void *read_blob_data_from_index(struct index_state *, const char *, unsig\n extern int ie_match_stat(const struct index_state *, const struct cache_entry *, struct stat *, unsigned int);\n extern int ie_modified(const struct index_state *, const struct cache_entry *, struct stat *, unsigned int);\n \n-#define PATHSPEC_ONESTAR 1\t/* the pathspec pattern sastisfies GFNM_ONESTAR */\n+#define PATHSPEC_ONESTAR 1\t/* the pathspec pattern satisfies GFNM_ONESTAR */\n \n struct pathspec {\n \tconst char **raw; /* get_pathspec() result, not freed by free_pathspec() */\ndiff --git a/Documentation/technical/api-revision-walking.txt b/Documentation/technical/api-revision-walking.txt\nindex b7d0d9a..55b878a 100644\n--- a/Documentation/technical/api-revision-walking.txt\n+++ b/Documentation/technical/api-revision-walking.txt\n@@ -59,7 +59,7 @@ function.\n `reset_revision_walk`::\n \n \tReset the flags used by the revision walking api. You can use\n-\tthis to do multiple sequencial revision walks.\n+\tthis to do multiple sequential revision walks.\n \n Data structures\n ---------------\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex e0b923f..8420aff 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -434,11 +434,11 @@ core.repositoryFormatVersion::\n \tversion.\n \n core.sharedRepository::\n-\tWhen 'group' (or 'true'), the repository is made shareable between\n+\tWhen 'group' (or 'true'), the repository is made sharable between\n \tseveral users in a group (making sure all the files and objects are\n \tgroup-writable). When 'all' (or 'world' or 'everybody'), the\n \trepository will be readable by all users, additionally to being\n-\tgroup-shareable. When 'umask' (or 'false'), Git will use permissions\n+\tgroup-sharable. When 'umask' (or 'false'), Git will use permissions\n \treported by umask(2). When '0xxx', where '0xxx' is an octal number,\n \tfiles in the repository will have this mode value. '0xxx' will override\n \tuser's umask value (whereas the other options will only override\ndiff --git a/contrib/ciabot/ciabot.sh b/contrib/ciabot/ciabot.sh\nindex 3fbbc53..dfb71a1 100755\n--- a/contrib/ciabot/ciabot.sh\n+++ b/contrib/ciabot/ciabot.sh\n@@ -64,7 +64,7 @@\n # down. It is unknown whether this is still an issue in 2010, but\n # XML-RPC would be annoying to do from sh in any case. (XML-RPC does\n # have the advantage that it guarantees notification of multiple commits\n-# shpped from an update in their actual order.)\n+# shipped from an update in their actual order.)\n #\n \n # The project as known to CIA. You can set this with a -p option,\ndiff --git a/Documentation/git-clean.txt b/Documentation/git-clean.txt\nindex 75fb543..1d3a082 100644\n--- a/Documentation/git-clean.txt\n+++ b/Documentation/git-clean.txt\n@@ -98,7 +98,7 @@ clean::\n filter by pattern::\n \n    This shows the files and directories to be deleted and issues an\n-   \"Input ignore patterns>>\" prompt. You can input space-seperated\n+   \"Input ignore patterns>>\" prompt. You can input space-separated\n    patterns to exclude files and directories from deletion.\n    E.g. \"*.c *.h\" will excludes files end with \".c\" and \".h\" from\n    deletion. When you are satisfied with the filtered result, press\ndiff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\nindex fe723e4..1491d69 100644\n--- a/Documentation/user-manual.txt\n+++ b/Documentation/user-manual.txt\n@@ -3116,7 +3116,7 @@ Trust\n If you receive the SHA-1 name of a blob from one source, and its contents\n from another (possibly untrusted) source, you can still trust that those\n contents are correct as long as the SHA-1 name agrees.  This is because\n-the SHA-1 is designed so that it is infeasible to find different contents\n+the SHA-1 is designed so that it is unfeasible to find different contents\n that produce the same hash.\n \n Similarly, you need only trust the SHA-1 name of a top-level tree object\n"},{"id":"224214","messageId":"CAGyf7-GBtOjM+PiA2oO4+oXZGKMQ+Lt9DpjSh0=7ma+HFz0p=w@mail.gmail.com","threadId":"34558","inReplyTo":"CAGyf7-FCj=x9e54Z0o2GmpQeNNeqHKDhHxWP5XqMt5Sfs8i2wg@mail.gmail.com","subject":"Re: [PATCH] More typofixes.","fromName":"Bryan Turner","fromEmail":"bturner@atlassian.com","sentAt":"2013-07-29T09:18:26Z","receivedAt":"2013-07-29T09:18:26Z","isPatch":true,"sender":{"key":"bturner@atlassian.com","avatar":"https://gravatar.com/avatar/16bcf3167981c1ef7c804e502642366d888a35b0d0b0a4ca01fdc442aa1acb1e?d=mp&s=160"},"body":"> diff --git a/pathspec.c b/pathspec.c\n> index 6ea0867..27ffe77 100644\n> --- a/pathspec.c\n> +++ b/pathspec.c\n> @@ -40,7 +40,7 @@ void add_pathspec_matches_against_index(const char **pathspec,\n>  /*\n>   * Finds which of the given pathspecs match items in the index.\n>   *\n> - * This is a one-shot wrapper around add_pathspec_matches_against_index()\n> + * This is an one-shot wrapper around add_pathspec_matches_against_index()\n>   * which allocates, populates, and returns a seen[] array indicating the\n>   * nature of the \"closest\" (i.e. most specific) matches which each of the\n>   * given pathspecs achieves against all items in the index.\n>\n>\n> diff --git a/builtin/log.c b/builtin/log.c\n> index 2625f98..01b49b3 100644\n> --- a/builtin/log.c\n> +++ b/builtin/log.c\n> @@ -304,7 +304,7 @@ static void setup_early_output(struct rev_info *rev)\n>          * tenth of a second, don't even bother doing the\n>          * early-output thing..\n>          *\n> -        * This is a one-time-only trigger.\n> +        * This is an one-time-only trigger.\n>          */\n>         early_output_timer.it_value.tv_sec = 0;\n>         early_output_timer.it_value.tv_usec = 100000;\n\nThese two are not typos. \"This is a one-time\" is grammatically correct.\n\n>\n> diff --git a/commit-slab.h b/commit-slab.h\n> index 7d48163..4f1c796 100644\n> --- a/commit-slab.h\n> +++ b/commit-slab.h\n> @@ -22,7 +22,7 @@\n>   *\n>   *   Initializes the indegree slab that associates an array of integers\n>   *   to each commit. 'stride' specifies how big each array is.  The slab\n> - *   that id initialied by the variant without \"_with_stride\" associates\n> + *   that id initialized by the variant without \"_with_stride\" associates\n>   *   each commit with an array of one integer.\n>   */\n\nTo my reading, it seems like that \"id\" should be \"is\", in addition to\nthe typo with \"initialized\"\n\nThat's a pretty impressive list of corrections.\n\nReviewed-by: Bryan Turner <bturner@atlassian.com>\n"},{"id":"224215","messageId":"CAJDDKr4M-QjbiF6Yu=JKYvGP1QVm4MwkU0q8d0gDXtys3VAiog@mail.gmail.com","threadId":"34558","inReplyTo":"20130729081821.GA6758@domone.kolej.mff.cuni.cz","subject":"Re: [PATCH] More typofixes.","fromName":"David Aguilar","fromEmail":"davvid@gmail.com","sentAt":"2013-07-29T09:40:57Z","receivedAt":"2013-07-29T09:40:57Z","isPatch":true,"sender":{"key":"davvid@gmail.com","avatar":"https://avatars.githubusercontent.com/u/13196?v=4"},"body":"On Mon, Jul 29, 2013 at 1:18 AM, Ondřej Bílka <neleai@seznam.cz> wrote:\n> Hi,\n>\n> I improved my tool and it catched following additional typos.\n>\n> As with any big project best way to catch errors is to have automated\n> checks that catch them ( Other possibility would be to read everything ten\n> times to get error rate down but nobody wants to do it).\n>\n> If you want you could add a pre-commit hook\n> stylepp-spellcheck --hook\n> that checks comments for likely typos (misspells by aspell and not\n> occurring in code). It uses aspell to identify them so you need to\n> teach aspell which words are valid.\n>\n> I would like make possible to share dictionaries so teaching phase can\n> be done only once instead for each person but I did not found suitable\n> workflow yet.\n>\n>\n> Signed-off-by: Ondřej Bílka <neleai@seznam.cz>\n>\n> diff --git a/pathspec.c b/pathspec.c\n> index 6ea0867..27ffe77 100644\n> --- a/pathspec.c\n> +++ b/pathspec.c\n> @@ -40,7 +40,7 @@ void add_pathspec_matches_against_index(const char **pathspec,\n>  /*\n>   * Finds which of the given pathspecs match items in the index.\n>   *\n> - * This is a one-shot wrapper around add_pathspec_matches_against_index()\n> + * This is an one-shot wrapper around add_pathspec_matches_against_index()\n\n\"one\" is pronounced like \"wun\" so we use \"a\" instead of \"an\" here.\nThese should stay as-is.\n-- \nDavid\n"},{"id":"224217","messageId":"CALkWK0m_vaOK6vDaauMsaUh91mDNqeyz2kDvFNoq+ruwztvDiA@mail.gmail.com","threadId":"34558","inReplyTo":"20130729081821.GA6758@domone.kolej.mff.cuni.cz","subject":"Re: [PATCH] More typofixes.","fromName":"Ramkumar Ramachandra","fromEmail":"artagnon@gmail.com","sentAt":"2013-07-29T10:26:31Z","receivedAt":"2013-07-29T10:26:31Z","isPatch":true,"sender":{"key":"r@artagnon.com","avatar":"https://avatars.githubusercontent.com/u/37226?v=4"},"body":"Ondřej Bílka wrote:\n> diff --git a/builtin/log.c b/builtin/log.c\n> index 2625f98..01b49b3 100644\n> --- a/builtin/log.c\n> +++ b/builtin/log.c\n> @@ -304,7 +304,7 @@ static void setup_early_output(struct rev_info *rev)\n>          * tenth of a second, don't even bother doing the\n>          * early-output thing..\n>          *\n> -        * This is a one-time-only trigger.\n> +        * This is an one-time-only trigger.\n\nI didn't look through your patch in detail, but this one caught my\neye: it's incorrect.\n"},{"id":"224219","messageId":"51F6826D.2010606@xiplink.com","threadId":"34558","inReplyTo":"20130729081821.GA6758@domone.kolej.mff.cuni.cz","subject":"Re: [PATCH] More typofixes.","fromName":"Marc Branchaud","fromEmail":"marcnarc@xiplink.com","sentAt":"2013-07-29T14:55:41Z","receivedAt":"2013-07-29T14:55:41Z","isPatch":true,"sender":{"key":"marcnarc@xiplink.com","avatar":"https://avatars.githubusercontent.com/u/14980203?v=4"},"body":"On 13-07-29 04:18 AM, Ondřej Bílka wrote:\n> Hi,\n> \n> I improved my tool and it catched following additional typos.\n> \n> As with any big project best way to catch errors is to have automated\n> checks that catch them ( Other possibility would be to read everything ten\n> times to get error rate down but nobody wants to do it).\n> \n> If you want you could add a pre-commit hook \n> stylepp-spellcheck --hook\n> that checks comments for likely typos (misspells by aspell and not\n> occurring in code). It uses aspell to identify them so you need to \n> teach aspell which words are valid. \n> \n> I would like make possible to share dictionaries so teaching phase can\n> be done only once instead for each person but I did not found suitable\n> workflow yet.\n\nUnfortunately no automated system is perfect (see some of my comments below).\n I'm all for an automated system that identifies potential misspellings, but\nI'm wary of anything that attempts to automatically correct perceived errors,\nor that can't be overruled.  In the end a human must make the final decision.\n\n> Signed-off-by: Ondřej Bílka <neleai@seznam.cz>\n> \n> diff --git a/pathspec.c b/pathspec.c\n> index 6ea0867..27ffe77 100644\n> --- a/pathspec.c\n> +++ b/pathspec.c\n> @@ -40,7 +40,7 @@ void add_pathspec_matches_against_index(const char **pathspec,\n>  /*\n>   * Finds which of the given pathspecs match items in the index.\n>   *\n> - * This is a one-shot wrapper around add_pathspec_matches_against_index()\n> + * This is an one-shot wrapper around add_pathspec_matches_against_index()\n\nAs many others have already said, this is not a typo.\n\nThe use of \"a\" or \"an\" depends on whether or not the O's sound is hard or\nsoft.  So although we say \"an orange\" we also say \"a one-in-a-million chance\".\n\n> \n>  [ ... snip ... ]\n> \n\n> diff --git a/Documentation/RelNotes/1.7.9.1.txt b/Documentation/RelNotes/1.7.9.1.txt\n> index 6957183..e8fddb8 100644\n> --- a/Documentation/RelNotes/1.7.9.1.txt\n> +++ b/Documentation/RelNotes/1.7.9.1.txt\n> @@ -20,7 +20,7 @@ Fixes since v1.7.9\n>     submodule that only has uncommitted local changes in the patch\n>     prepared by for the user to edit.\n>  \n> - * Typo in \"git branch --edit-description my-tpoic\" was not diagnosed.\n> + * Typo in \"git branch --edit-description my-topic\" was not diagnosed.\n\nHere \"tpoic\" is illustrating the typo that was being misdiagnosed.\n\n> \n>  [ ... snip ... ]\n> \n\n> diff --git a/Documentation/config.txt b/Documentation/config.txt\n> index e0b923f..8420aff 100644\n> --- a/Documentation/config.txt\n> +++ b/Documentation/config.txt\n> @@ -434,11 +434,11 @@ core.repositoryFormatVersion::\n>  \tversion.\n>  \n>  core.sharedRepository::\n> -\tWhen 'group' (or 'true'), the repository is made shareable between\n> +\tWhen 'group' (or 'true'), the repository is made sharable between\n>  \tseveral users in a group (making sure all the files and objects are\n>  \tgroup-writable). When 'all' (or 'world' or 'everybody'), the\n>  \trepository will be readable by all users, additionally to being\n> -\tgroup-shareable. When 'umask' (or 'false'), Git will use permissions\n> +\tgroup-sharable. When 'umask' (or 'false'), Git will use permissions\n\n\"Sharable\" is the North American spelling.  AFAIK git doesn't specify what\nkind of English the documentation source files should use.  Perhaps one day\nthere'll be en_UK and en_US translations, and all the sources will be written\nin Klingon...\n\nUntil that day, or until the git project starts to care a lot more about\nEnglish style, I think patches that translate spellings between English\nvariants are a bit of a waste of time.\n\n> \n>  [ ... snip ... ]\n> \n\n> diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\n> index fe723e4..1491d69 100644\n> --- a/Documentation/user-manual.txt\n> +++ b/Documentation/user-manual.txt\n> @@ -3116,7 +3116,7 @@ Trust\n>  If you receive the SHA-1 name of a blob from one source, and its contents\n>  from another (possibly untrusted) source, you can still trust that those\n>  contents are correct as long as the SHA-1 name agrees.  This is because\n> -the SHA-1 is designed so that it is infeasible to find different contents\n> +the SHA-1 is designed so that it is unfeasible to find different contents\n>  that produce the same hash.\n>  \n>  Similarly, you need only trust the SHA-1 name of a top-level tree object\n\nBoth \"infeasible\" and \"unfeasible\" are in common usage.  If you want to avoid\nfuture patches going back and forth on this, try \"not feasible\".\n\n\t\tM.\n"},{"id":"224227","messageId":"20130729153849.GA8111@domone.kolej.mff.cuni.cz","threadId":"34558","inReplyTo":"51F6826D.2010606@xiplink.com","subject":"Re: [PATCH] More typofixes.","fromName":"Ondřej Bílka","fromEmail":"neleai@seznam.cz","sentAt":"2013-07-29T15:38:49Z","receivedAt":"2013-07-29T15:38:49Z","isPatch":true,"sender":{"key":"neleai@seznam.cz","avatar":"https://avatars.githubusercontent.com/u/48067?v=4"},"body":"On Mon, Jul 29, 2013 at 10:55:41AM -0400, Marc Branchaud wrote:\n> On 13-07-29 04:18 AM, Ondřej Bílka wrote:\n> > Hi,\n> > \n> > I improved my tool and it catched following additional typos.\n> > \n> > As with any big project best way to catch errors is to have automated\n> > checks that catch them ( Other possibility would be to read everything ten\n> > times to get error rate down but nobody wants to do it).\n> > \n> > If you want you could add a pre-commit hook \n> > stylepp-spellcheck --hook\n> > that checks comments for likely typos (misspells by aspell and not\n> > occurring in code). It uses aspell to identify them so you need to \n> > teach aspell which words are valid. \n> > \n> > I would like make possible to share dictionaries so teaching phase can\n> > be done only once instead for each person but I did not found suitable\n> > workflow yet.\n> \n> Unfortunately no automated system is perfect (see some of my comments below).\n>  I'm all for an automated system that identifies potential misspellings, but\n\n> > that checks comments for likely typos (misspells by aspell and not\n> > occurring in code)\n\nIt just prints likely typos, nothing more. \n\n> I'm wary of anything that attempts to automatically correct perceived errors,\n> or that can't be overruled.  In the end a human must make the final decision.\n> \nIts more about minimizing time human must spend to review.\nIt is faster to read sentences with corrections and check if they make\nsense and fix few that do not than switching between find typo, \nread sentence, look up alternatives, decide which one makes sense.\n\nIt is natural that there will be errors in generated corrections; I lack\nneccessary domain knowledge for start.\n\n> > Signed-off-by: Ondřej Bílka <neleai@seznam.cz>\n> > \n> > diff --git a/pathspec.c b/pathspec.c\n> > index 6ea0867..27ffe77 100644\n> > --- a/pathspec.c\n> > +++ b/pathspec.c\n> > @@ -40,7 +40,7 @@ void add_pathspec_matches_against_index(const char **pathspec,\n> >  /*\n> >   * Finds which of the given pathspecs match items in the index.\n> >   *\n> > - * This is a one-shot wrapper around add_pathspec_matches_against_index()\n> > + * This is an one-shot wrapper around add_pathspec_matches_against_index()\n> \n> As many others have already said, this is not a typo.\n> \n> The use of \"a\" or \"an\" depends on whether or not the O's sound is hard or\n> soft.  So although we say \"an orange\" we also say \"a one-in-a-million chance\".\n> \nWell it slipped through my filter and review. Ideally a script could\njust look up pronunciation in dictionary but I did not find downloadable\none yet.\n\n> > \n> >  [ ... snip ... ]\n> > \n> \n> > diff --git a/Documentation/RelNotes/1.7.9.1.txt b/Documentation/RelNotes/1.7.9.1.txt\n> > index 6957183..e8fddb8 100644\n> > --- a/Documentation/RelNotes/1.7.9.1.txt\n> > +++ b/Documentation/RelNotes/1.7.9.1.txt\n> > @@ -20,7 +20,7 @@ Fixes since v1.7.9\n> >     submodule that only has uncommitted local changes in the patch\n> >     prepared by for the user to edit.\n> >  \n> > - * Typo in \"git branch --edit-description my-tpoic\" was not diagnosed.\n> > + * Typo in \"git branch --edit-description my-topic\" was not diagnosed.\n> \n> Here \"tpoic\" is illustrating the typo that was being misdiagnosed.\n> \nyes, domain knowledge.\n> > \n> >  [ ... snip ... ]\n> > \n> \n> > diff --git a/Documentation/config.txt b/Documentation/config.txt\n> > index e0b923f..8420aff 100644\n> > --- a/Documentation/config.txt\n> > +++ b/Documentation/config.txt\n> > @@ -434,11 +434,11 @@ core.repositoryFormatVersion::\n> >  \tversion.\n> >  \n> >  core.sharedRepository::\n> > -\tWhen 'group' (or 'true'), the repository is made shareable between\n> > +\tWhen 'group' (or 'true'), the repository is made sharable between\n> >  \tseveral users in a group (making sure all the files and objects are\n> >  \tgroup-writable). When 'all' (or 'world' or 'everybody'), the\n> >  \trepository will be readable by all users, additionally to being\n> > -\tgroup-shareable. When 'umask' (or 'false'), Git will use permissions\n> > +\tgroup-sharable. When 'umask' (or 'false'), Git will use permissions\n> \n> \"Sharable\" is the North American spelling.  AFAIK git doesn't specify what\n> kind of English the documentation source files should use.  Perhaps one day\n> there'll be en_UK and en_US translations, and all the sources will be written\n> in Klingon...\n> \n> Until that day, or until the git project starts to care a lot more about\n> English style, I think patches that translate spellings between English\n> variants are a bit of a waste of time.\n> \nI need better dictionary that aspell currently has.\n\nMy replacements were mostly generated from commit histories of several projects\nwhere I looked when wrong word changes to correct one and letters stay\nmostly same. \n\nThis caused false positives like this.\n\n> > \n> >  [ ... snip ... ]\n> > \n> \n> > diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\n> > index fe723e4..1491d69 100644\n> > --- a/Documentation/user-manual.txt\n> > +++ b/Documentation/user-manual.txt\n> > @@ -3116,7 +3116,7 @@ Trust\n> >  If you receive the SHA-1 name of a blob from one source, and its contents\n> >  from another (possibly untrusted) source, you can still trust that those\n> >  contents are correct as long as the SHA-1 name agrees.  This is because\n> > -the SHA-1 is designed so that it is infeasible to find different contents\n> > +the SHA-1 is designed so that it is unfeasible to find different contents\n> >  that produce the same hash.\n> >  \n> >  Similarly, you need only trust the SHA-1 name of a top-level tree object\n> \n> Both \"infeasible\" and \"unfeasible\" are in common usage.  If you want to avoid\n> future patches going back and forth on this, try \"not feasible\".\n> \n> \t\tM.\n"},{"id":"224240","messageId":"7vob9l1d2s.fsf@alter.siamese.dyndns.org","threadId":"34558","inReplyTo":"51F6826D.2010606@xiplink.com","subject":"Re: [PATCH] More typofixes.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-07-29T17:38:19Z","receivedAt":"2013-07-29T17:38:19Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Marc Branchaud <marcnarc@xiplink.com> writes:\n\n> Unfortunately no automated system is perfect (see some of my comments below).\n>  I'm all for an automated system that identifies potential misspellings, but\n> I'm wary of anything that attempts to automatically correct perceived errors,\n> or that can't be overruled.  In the end a human must make the final decision.\n\nI'd actually prefer to see no patch that says \"this was done with an\nautomatic tool\".  You can use automation on your end all you want,\nbut the final result needs to be eyeballed before sending it out,\nand at that point both the credit and the blame lies on you, not any\nautomated tool.\n\n>>  core.sharedRepository::\n>> -\tWhen 'group' (or 'true'), the repository is made shareable between\n>> +\tWhen 'group' (or 'true'), the repository is made sharable between\n>>  \tseveral users in a group (making sure all the files and objects are\n>>  \tgroup-writable). When 'all' (or 'world' or 'everybody'), the\n>>  \trepository will be readable by all users, additionally to being\n>> -\tgroup-shareable. When 'umask' (or 'false'), Git will use permissions\n>> +\tgroup-sharable. When 'umask' (or 'false'), Git will use permissions\n>\n> \"Sharable\" is the North American spelling.  AFAIK git doesn't specify what\n> kind of English the documentation source files should use.  Perhaps one day\n> there'll be en_UK and en_US translations, and all the sources will be written\n> in Klingon...\n\n;-)\n\nIt often is a good idea to ask your search engine \"What is X\", and I\nseem to get a positive result for \"what is shareable\" just fine.\n"},{"id":"224242","messageId":"7vk3k91cfy.fsf@alter.siamese.dyndns.org","threadId":"34558","inReplyTo":"7vob9l1d2s.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] More typofixes.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-07-29T17:52:01Z","receivedAt":"2013-07-29T17:52:01Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Junio C Hamano <gitster@pobox.com> writes:\n\n> Marc Branchaud <marcnarc@xiplink.com> writes:\n>\n>> Unfortunately no automated system is perfect (see some of my comments below).\n>>  I'm all for an automated system that identifies potential misspellings, but\n>> I'm wary of anything that attempts to automatically correct perceived errors,\n>> or that can't be overruled.  In the end a human must make the final decision.\n>\n> I'd actually prefer to see no patch that says \"this was done with an\n> automatic tool\".  You can use automation on your end all you want,\n> but the final result needs to be eyeballed before sending it out,\n> and at that point both the credit and the blame lies on you, not any\n> automated tool.\n>\n>>>  core.sharedRepository::\n>>> -\tWhen 'group' (or 'true'), the repository is made shareable between\n>>> +\tWhen 'group' (or 'true'), the repository is made sharable between\n>>>  \tseveral users in a group (making sure all the files and objects are\n>>>  \tgroup-writable). When 'all' (or 'world' or 'everybody'), the\n>>>  \trepository will be readable by all users, additionally to being\n>>> -\tgroup-shareable. When 'umask' (or 'false'), Git will use permissions\n>>> +\tgroup-sharable. When 'umask' (or 'false'), Git will use permissions\n>>\n>> \"Sharable\" is the North American spelling.  AFAIK git doesn't specify what\n>> kind of English the documentation source files should use.  Perhaps one day\n>> there'll be en_UK and en_US translations, and all the sources will be written\n>> in Klingon...\n>\n> ;-)\n>\n> It often is a good idea to ask your search engine \"What is X\", and I\n> seem to get a positive result for \"what is shareable\" just fine.\n\nHere is what I salvaged for 'maint'.  Eyeballing by others is very\nmuch appreciated.\n\n-- >8 --\nFrom: Ondřej Bílka <neleai@seznam.cz>\nSubject: [PATCH] many small typofixes\nDate: Mon, 29 Jul 2013 10:18:21 +0200\n\nSigned-off-by: Ondřej Bílka <neleai@seznam.cz>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>\n---\n Documentation/howto/new-command.txt              | 2 +-\n Documentation/technical/api-revision-walking.txt | 2 +-\n builtin/fast-export.c                            | 2 +-\n builtin/push.c                                   | 2 +-\n cache.h                                          | 2 +-\n combine-diff.c                                   | 2 +-\n contrib/ciabot/ciabot.py                         | 2 +-\n contrib/ciabot/ciabot.sh                         | 4 ++--\n contrib/subtree/git-subtree.txt                  | 2 +-\n git-mergetool--lib.sh                            | 2 +-\n git-p4.py                                        | 2 +-\n notes.h                                          | 2 +-\n read-cache.c                                     | 4 ++--\n t/gitweb-lib.sh                                  | 2 +-\n t/lib-t6000.sh                                   | 2 +-\n t/t7601-merge-pull-config.sh                     | 2 +-\n t/t9020-remote-svn.sh                            | 2 +-\n t/t9112-git-svn-md5less-file.sh                  | 2 +-\n t/t9802-git-p4-filetype.sh                       | 2 +-\n transport-helper.c                               | 4 ++--\n 20 files changed, 23 insertions(+), 23 deletions(-)\n\ndiff --git a/Documentation/howto/new-command.txt b/Documentation/howto/new-command.txt\nindex 2abc3a0..d7de5a3 100644\n--- a/Documentation/howto/new-command.txt\n+++ b/Documentation/howto/new-command.txt\n@@ -94,7 +94,7 @@ your language, document it in the INSTALL file.\n 6. There is a file command-list.txt in the distribution main directory\n that categorizes commands by type, so they can be listed in appropriate\n subsections in the documentation's summary command list.  Add an entry\n-for yours.  To understand the categories, look at git-cmmands.txt\n+for yours.  To understand the categories, look at git-commands.txt\n in the main directory.\n \n 7. Give the maintainer one paragraph to include in the RelNotes file\ndiff --git a/Documentation/technical/api-revision-walking.txt b/Documentation/technical/api-revision-walking.txt\nindex b7d0d9a..55b878a 100644\n--- a/Documentation/technical/api-revision-walking.txt\n+++ b/Documentation/technical/api-revision-walking.txt\n@@ -59,7 +59,7 @@ function.\n `reset_revision_walk`::\n \n \tReset the flags used by the revision walking api. You can use\n-\tthis to do multiple sequencial revision walks.\n+\tthis to do multiple sequential revision walks.\n \n Data structures\n ---------------\ndiff --git a/builtin/fast-export.c b/builtin/fast-export.c\nindex d60d675..0c8d250 100644\n--- a/builtin/fast-export.c\n+++ b/builtin/fast-export.c\n@@ -379,7 +379,7 @@ static void handle_tag(const char *name, struct tag *tag)\n \tint tagged_mark;\n \tstruct commit *p;\n \n-\t/* Trees have no identifer in fast-export output, thus we have no way\n+\t/* Trees have no identifier in fast-export output, thus we have no way\n \t * to output tags of trees, tags of tags of trees, etc.  Simply omit\n \t * such tags.\n \t */\ndiff --git a/builtin/push.c b/builtin/push.c\nindex 2d84d10..795197a 100644\n--- a/builtin/push.c\n+++ b/builtin/push.c\n@@ -92,7 +92,7 @@ static NORETURN int die_push_simple(struct branch *branch, struct remote *remote\n \tif (!short_upstream)\n \t\tshort_upstream = branch->merge[0]->src;\n \t/*\n-\t * Don't show advice for people who explicitely set\n+\t * Don't show advice for people who explicitly set\n \t * push.default.\n \t */\n \tif (push_default == PUSH_DEFAULT_UNSPECIFIED)\ndiff --git a/cache.h b/cache.h\nindex 94ca1ac..5794479 100644\n--- a/cache.h\n+++ b/cache.h\n@@ -483,7 +483,7 @@ extern void *read_blob_data_from_index(struct index_state *, const char *, unsig\n extern int ie_match_stat(const struct index_state *, struct cache_entry *, struct stat *, unsigned int);\n extern int ie_modified(const struct index_state *, struct cache_entry *, struct stat *, unsigned int);\n \n-#define PATHSPEC_ONESTAR 1\t/* the pathspec pattern sastisfies GFNM_ONESTAR */\n+#define PATHSPEC_ONESTAR 1\t/* the pathspec pattern satisfies GFNM_ONESTAR */\n \n struct pathspec {\n \tconst char **raw; /* get_pathspec() result, not freed by free_pathspec() */\ndiff --git a/combine-diff.c b/combine-diff.c\nindex 6dc0609..88525b3 100644\n--- a/combine-diff.c\n+++ b/combine-diff.c\n@@ -165,7 +165,7 @@ static struct lline *coalesce_lines(struct lline *base, int *lenbase,\n \n \t/*\n \t * Coalesce new lines into base by finding the LCS\n-\t * - Create the table to run dynamic programing\n+\t * - Create the table to run dynamic programming\n \t * - Compute the LCS\n \t * - Then reverse read the direction structure:\n \t *   - If we have MATCH, assign parent to base flag, and consume\ndiff --git a/contrib/ciabot/ciabot.py b/contrib/ciabot/ciabot.py\nindex 36b5665..befa0c3 100755\n--- a/contrib/ciabot/ciabot.py\n+++ b/contrib/ciabot/ciabot.py\n@@ -70,7 +70,7 @@ tinyifier = \"http://tinyurl.com/api-create.php?url=\"\n \n # The template used to generate the XML messages to CIA.  You can make\n # visible changes to the IRC-bot notification lines by hacking this.\n-# The default will produce a notfication line that looks like this:\n+# The default will produce a notification line that looks like this:\n #\n # ${project}: ${author} ${repo}:${branch} * ${rev} ${files}: ${logmsg} ${url}\n #\ndiff --git a/contrib/ciabot/ciabot.sh b/contrib/ciabot/ciabot.sh\nindex 3fbbc53..dfb71a1 100755\n--- a/contrib/ciabot/ciabot.sh\n+++ b/contrib/ciabot/ciabot.sh\n@@ -39,7 +39,7 @@\n #       done\n #\n # The reason for the tac call is that git rev-list emits commits from\n-# most recent to least - better to ship notifactions from oldest to newest.\n+# most recent to least - better to ship notifications from oldest to newest.\n #\n # Configuration variables affecting this script:\n #\n@@ -64,7 +64,7 @@\n # down. It is unknown whether this is still an issue in 2010, but\n # XML-RPC would be annoying to do from sh in any case. (XML-RPC does\n # have the advantage that it guarantees notification of multiple commits\n-# shpped from an update in their actual order.)\n+# shipped from an update in their actual order.)\n #\n \n # The project as known to CIA. You can set this with a -p option,\ndiff --git a/contrib/subtree/git-subtree.txt b/contrib/subtree/git-subtree.txt\nindex 7ba853e..e0957ee 100644\n--- a/contrib/subtree/git-subtree.txt\n+++ b/contrib/subtree/git-subtree.txt\n@@ -270,7 +270,7 @@ git-extensions repository in ~/git-extensions/:\n name\n \n You can omit the --squash flag, but doing so will increase the number\n-of commits that are incldued in your local repository.\n+of commits that are included in your local repository.\n \n We now have a ~/git-extensions/git-subtree directory containing code\n from the master branch of git://github.com/apenwarr/git-subtree.git\ndiff --git a/git-mergetool--lib.sh b/git-mergetool--lib.sh\nindex e338be5..7e5c525 100644\n--- a/git-mergetool--lib.sh\n+++ b/git-mergetool--lib.sh\n@@ -117,7 +117,7 @@ valid_tool () {\n setup_tool () {\n \ttool=\"$1\"\n \n-\t# Fallback definitions, to be overriden by tools.\n+\t# Fallback definitions, to be overridden by tools.\n \tcan_merge () {\n \t\treturn 0\n \t}\ndiff --git a/git-p4.py b/git-p4.py\nindex 88fcf23..31e71ff 100755\n--- a/git-p4.py\n+++ b/git-p4.py\n@@ -1786,7 +1786,7 @@ class P4Submit(Command, P4UserMap):\n             missingGitTags = gitTags - p4Labels\n             self.exportGitTags(missingGitTags)\n \n-        # exit with error unless everything applied perfecly\n+        # exit with error unless everything applied perfectly\n         if len(commits) != len(applied):\n                 sys.exit(1)\n \ndiff --git a/notes.h b/notes.h\nindex 3324c48..2a3f923 100644\n--- a/notes.h\n+++ b/notes.h\n@@ -77,7 +77,7 @@ const char *default_notes_ref(void);\n  * variable is used, and if that is missing, the default notes ref is used\n  * (\"refs/notes/commits\").\n  *\n- * If you need to re-intialize a notes_tree structure (e.g. when switching from\n+ * If you need to re-initialize a notes_tree structure (e.g. when switching from\n  * one notes ref to another), you must first de-initialize the notes_tree\n  * structure by calling free_notes(struct notes_tree *).\n  *\ndiff --git a/read-cache.c b/read-cache.c\nindex d97e3bf..fe7da6c 100644\n--- a/read-cache.c\n+++ b/read-cache.c\n@@ -472,7 +472,7 @@ int remove_index_entry_at(struct index_state *istate, int pos)\n }\n \n /*\n- * Remove all cache ententries marked for removal, that is where\n+ * Remove all cache entries marked for removal, that is where\n  * CE_REMOVE is set in ce_flags.  This is much more effective than\n  * calling remove_index_entry_at() for each entry to be removed.\n  */\n@@ -1743,7 +1743,7 @@ static int has_racy_timestamp(struct index_state *istate)\n }\n \n /*\n- * Opportunisticly update the index but do not complain if we can't\n+ * Opportunistically update the index but do not complain if we can't\n  */\n void update_index_if_able(struct index_state *istate, struct lock_file *lockfile)\n {\ndiff --git a/t/gitweb-lib.sh b/t/gitweb-lib.sh\nindex ae2dc46..9e381e0 100644\n--- a/t/gitweb-lib.sh\n+++ b/t/gitweb-lib.sh\n@@ -36,7 +36,7 @@ EOF\n \n \t# You can set the GITWEB_TEST_INSTALLED environment variable to\n \t# the gitwebdir (the directory where gitweb is installed / deployed to)\n-\t# of an existing gitweb instalation to test that installation,\n+\t# of an existing gitweb installation to test that installation,\n \t# or simply to pathname of installed gitweb script.\n \tif test -n \"$GITWEB_TEST_INSTALLED\" ; then\n \t\tif test -d $GITWEB_TEST_INSTALLED; then\ndiff --git a/t/lib-t6000.sh b/t/lib-t6000.sh\nindex ea25dd8..4a397e6 100644\n--- a/t/lib-t6000.sh\n+++ b/t/lib-t6000.sh\n@@ -37,7 +37,7 @@ save_tag()\n \tmv sed.script.tmp sed.script\n }\n \n-# Replace unhelpful sha1 hashses with their symbolic equivalents\n+# Replace unhelpful sha1 hashes with their symbolic equivalents\n entag()\n {\n \tsed -f sed.script\ndiff --git a/t/t7601-merge-pull-config.sh b/t/t7601-merge-pull-config.sh\nindex 25dac79..830a4c3 100755\n--- a/t/t7601-merge-pull-config.sh\n+++ b/t/t7601-merge-pull-config.sh\n@@ -109,7 +109,7 @@ test_expect_success 'setup conflicted merge' '\n '\n \n # First do the merge with resolve and recursive then verify that\n-# recusive is chosen.\n+# recursive is chosen.\n \n test_expect_success 'merge picks up the best result' '\n \tgit config --unset-all pull.twohead &&\ndiff --git a/t/t9020-remote-svn.sh b/t/t9020-remote-svn.sh\nindex d9f6b73..4d81ba1 100755\n--- a/t/t9020-remote-svn.sh\n+++ b/t/t9020-remote-svn.sh\n@@ -24,7 +24,7 @@ init_git () {\n \trm -fr .git &&\n \tgit init &&\n \t#git remote add svnsim testsvn::sim:///$TEST_DIRECTORY/t9020/example.svnrdump\n-\t# let's reuse an exisiting dump file!?\n+\t# let's reuse an existing dump file!?\n \tgit remote add svnsim testsvn::sim://$TEST_DIRECTORY/t9154/svn.dump\n \tgit remote add svnfile testsvn::file://$TEST_DIRECTORY/t9154/svn.dump\n }\ndiff --git a/t/t9112-git-svn-md5less-file.sh b/t/t9112-git-svn-md5less-file.sh\nindex a61d671..9861c71 100755\n--- a/t/t9112-git-svn-md5less-file.sh\n+++ b/t/t9112-git-svn-md5less-file.sh\n@@ -7,7 +7,7 @@ test_description='test that git handles an svn repository with missing md5sums'\n # Loading a node from a svn dumpfile without a Text-Content-Length\n # field causes svn to neglect to store or report an md5sum.  (it will\n # calculate one if you had put Text-Content-Length: 0).  This showed\n-# up in a repository creted with cvs2svn.\n+# up in a repository created with cvs2svn.\n \n cat > dumpfile.svn <<EOF\n SVN-fs-dump-format-version: 1\ndiff --git a/t/t9802-git-p4-filetype.sh b/t/t9802-git-p4-filetype.sh\nindex eeefa67..87f4968 100755\n--- a/t/t9802-git-p4-filetype.sh\n+++ b/t/t9802-git-p4-filetype.sh\n@@ -28,7 +28,7 @@ test_expect_success 'p4 client newlines, unix' '\n \t\ttest_cmp f-unix-orig f-unix &&\n \n \t\t# make sure stored in repo as unix newlines\n-\t\t# use sed to eat python-appened newline\n+\t\t# use sed to eat python-appended newline\n \t\tp4 -G print //depot/f-unix | marshal_dump data 2 |\\\n \t\t    sed \\$d >f-unix-p4-print &&\n \t\ttest_cmp f-unix-orig f-unix-p4-print &&\ndiff --git a/transport-helper.c b/transport-helper.c\nindex 522d791..2ba3012 100644\n--- a/transport-helper.c\n+++ b/transport-helper.c\n@@ -1104,7 +1104,7 @@ static void *udt_copy_task_routine(void *udt)\n #ifndef NO_PTHREADS\n \n /*\n- * Join thread, with apporiate errors on failure. Name is name for the\n+ * Join thread, with appropriate errors on failure. Name is name for the\n  * thread (for error messages). Returns 0 on success, 1 on failure.\n  */\n static int tloop_join(pthread_t thread, const char *name)\n@@ -1170,7 +1170,7 @@ static void udt_kill_transfer(struct unidirectional_transfer *t)\n }\n \n /*\n- * Join process, with apporiate errors on failure. Name is name for the\n+ * Join process, with appropriate errors on failure. Name is name for the\n  * process (for error messages). Returns 0 on success, 1 on failure.\n  */\n static int tloop_join(pid_t pid, const char *name)\n"},{"id":"224245","messageId":"51F6AD93.7090601@googlemail.com","threadId":"34558","inReplyTo":"7vk3k91cfy.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] More typofixes.","fromName":"Stefan Beller","fromEmail":"stefanbeller@googlemail.com","sentAt":"2013-07-29T17:59:47Z","receivedAt":"2013-07-29T17:59:47Z","isPatch":true,"sender":{"key":"stefanbeller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/455868?v=4"},"body":"On 07/29/2013 07:52 PM, Junio C Hamano wrote:\n> Junio C Hamano <gitster@pobox.com> writes:\n> \n>> Marc Branchaud <marcnarc@xiplink.com> writes:\n>>\n>>> Unfortunately no automated system is perfect (see some of my comments below).\n>>>  I'm all for an automated system that identifies potential misspellings, but\n>>> I'm wary of anything that attempts to automatically correct perceived errors,\n>>> or that can't be overruled.  In the end a human must make the final decision.\n>>\n>> I'd actually prefer to see no patch that says \"this was done with an\n>> automatic tool\".  You can use automation on your end all you want,\n>> but the final result needs to be eyeballed before sending it out,\n>> and at that point both the credit and the blame lies on you, not any\n>> automated tool.\n>>\n>>>>  core.sharedRepository::\n>>>> -\tWhen 'group' (or 'true'), the repository is made shareable between\n>>>> +\tWhen 'group' (or 'true'), the repository is made sharable between\n>>>>  \tseveral users in a group (making sure all the files and objects are\n>>>>  \tgroup-writable). When 'all' (or 'world' or 'everybody'), the\n>>>>  \trepository will be readable by all users, additionally to being\n>>>> -\tgroup-shareable. When 'umask' (or 'false'), Git will use permissions\n>>>> +\tgroup-sharable. When 'umask' (or 'false'), Git will use permissions\n>>>\n>>> \"Sharable\" is the North American spelling.  AFAIK git doesn't specify what\n>>> kind of English the documentation source files should use.  Perhaps one day\n>>> there'll be en_UK and en_US translations, and all the sources will be written\n>>> in Klingon...\n>>\n>> ;-)\n>>\n>> It often is a good idea to ask your search engine \"What is X\", and I\n>> seem to get a positive result for \"what is shareable\" just fine.\n> \n> Here is what I salvaged for 'maint'.  Eyeballing by others is very\n> much appreciated.\n> \n> -- >8 --\n> From: Ondřej Bílka <neleai@seznam.cz>\n> Subject: [PATCH] many small typofixes\n> Date: Mon, 29 Jul 2013 10:18:21 +0200\n> \n> Signed-off-by: Ondřej Bílka <neleai@seznam.cz>\n> Signed-off-by: Junio C Hamano <gitster@pobox.com>\n> ---\n>  Documentation/howto/new-command.txt              | 2 +-\n>  Documentation/technical/api-revision-walking.txt | 2 +-\n>  builtin/fast-export.c                            | 2 +-\n>  builtin/push.c                                   | 2 +-\n>  cache.h                                          | 2 +-\n>  combine-diff.c                                   | 2 +-\n>  contrib/ciabot/ciabot.py                         | 2 +-\n>  contrib/ciabot/ciabot.sh                         | 4 ++--\n>  contrib/subtree/git-subtree.txt                  | 2 +-\n>  git-mergetool--lib.sh                            | 2 +-\n>  git-p4.py                                        | 2 +-\n>  notes.h                                          | 2 +-\n>  read-cache.c                                     | 4 ++--\n>  t/gitweb-lib.sh                                  | 2 +-\n>  t/lib-t6000.sh                                   | 2 +-\n>  t/t7601-merge-pull-config.sh                     | 2 +-\n>  t/t9020-remote-svn.sh                            | 2 +-\n>  t/t9112-git-svn-md5less-file.sh                  | 2 +-\n>  t/t9802-git-p4-filetype.sh                       | 2 +-\n>  transport-helper.c                               | 4 ++--\n>  20 files changed, 23 insertions(+), 23 deletions(-)\n> \n> diff --git a/Documentation/howto/new-command.txt b/Documentation/howto/new-command.txt\n> index 2abc3a0..d7de5a3 100644\n> --- a/Documentation/howto/new-command.txt\n> +++ b/Documentation/howto/new-command.txt\n> @@ -94,7 +94,7 @@ your language, document it in the INSTALL file.\n>  6. There is a file command-list.txt in the distribution main directory\n>  that categorizes commands by type, so they can be listed in appropriate\n>  subsections in the documentation's summary command list.  Add an entry\n> -for yours.  To understand the categories, look at git-cmmands.txt\n> +for yours.  To understand the categories, look at git-commands.txt\n>  in the main directory.\n>  \n>  7. Give the maintainer one paragraph to include in the RelNotes file\n> diff --git a/Documentation/technical/api-revision-walking.txt b/Documentation/technical/api-revision-walking.txt\n> index b7d0d9a..55b878a 100644\n> --- a/Documentation/technical/api-revision-walking.txt\n> +++ b/Documentation/technical/api-revision-walking.txt\n> @@ -59,7 +59,7 @@ function.\n>  `reset_revision_walk`::\n>  \n>  \tReset the flags used by the revision walking api. You can use\n> -\tthis to do multiple sequencial revision walks.\n> +\tthis to do multiple sequential revision walks.\n>  \n>  Data structures\n>  ---------------\n> diff --git a/builtin/fast-export.c b/builtin/fast-export.c\n> index d60d675..0c8d250 100644\n> --- a/builtin/fast-export.c\n> +++ b/builtin/fast-export.c\n> @@ -379,7 +379,7 @@ static void handle_tag(const char *name, struct tag *tag)\n>  \tint tagged_mark;\n>  \tstruct commit *p;\n>  \n> -\t/* Trees have no identifer in fast-export output, thus we have no way\n> +\t/* Trees have no identifier in fast-export output, thus we have no way\n>  \t * to output tags of trees, tags of tags of trees, etc.  Simply omit\n>  \t * such tags.\n>  \t */\n> diff --git a/builtin/push.c b/builtin/push.c\n> index 2d84d10..795197a 100644\n> --- a/builtin/push.c\n> +++ b/builtin/push.c\n> @@ -92,7 +92,7 @@ static NORETURN int die_push_simple(struct branch *branch, struct remote *remote\n>  \tif (!short_upstream)\n>  \t\tshort_upstream = branch->merge[0]->src;\n>  \t/*\n> -\t * Don't show advice for people who explicitely set\n> +\t * Don't show advice for people who explicitly set\n>  \t * push.default.\n>  \t */\n>  \tif (push_default == PUSH_DEFAULT_UNSPECIFIED)\n> diff --git a/cache.h b/cache.h\n> index 94ca1ac..5794479 100644\n> --- a/cache.h\n> +++ b/cache.h\n> @@ -483,7 +483,7 @@ extern void *read_blob_data_from_index(struct index_state *, const char *, unsig\n>  extern int ie_match_stat(const struct index_state *, struct cache_entry *, struct stat *, unsigned int);\n>  extern int ie_modified(const struct index_state *, struct cache_entry *, struct stat *, unsigned int);\n>  \n> -#define PATHSPEC_ONESTAR 1\t/* the pathspec pattern sastisfies GFNM_ONESTAR */\n> +#define PATHSPEC_ONESTAR 1\t/* the pathspec pattern satisfies GFNM_ONESTAR */\n>  \n>  struct pathspec {\n>  \tconst char **raw; /* get_pathspec() result, not freed by free_pathspec() */\n> diff --git a/combine-diff.c b/combine-diff.c\n> index 6dc0609..88525b3 100644\n> --- a/combine-diff.c\n> +++ b/combine-diff.c\n> @@ -165,7 +165,7 @@ static struct lline *coalesce_lines(struct lline *base, int *lenbase,\n>  \n>  \t/*\n>  \t * Coalesce new lines into base by finding the LCS\n> -\t * - Create the table to run dynamic programing\n> +\t * - Create the table to run dynamic programming\n>  \t * - Compute the LCS\n>  \t * - Then reverse read the direction structure:\n>  \t *   - If we have MATCH, assign parent to base flag, and consume\n> diff --git a/contrib/ciabot/ciabot.py b/contrib/ciabot/ciabot.py\n> index 36b5665..befa0c3 100755\n> --- a/contrib/ciabot/ciabot.py\n> +++ b/contrib/ciabot/ciabot.py\n> @@ -70,7 +70,7 @@ tinyifier = \"http://tinyurl.com/api-create.php?url=\"\n>  \n>  # The template used to generate the XML messages to CIA.  You can make\n>  # visible changes to the IRC-bot notification lines by hacking this.\n> -# The default will produce a notfication line that looks like this:\n> +# The default will produce a notification line that looks like this:\n>  #\n>  # ${project}: ${author} ${repo}:${branch} * ${rev} ${files}: ${logmsg} ${url}\n>  #\n> diff --git a/contrib/ciabot/ciabot.sh b/contrib/ciabot/ciabot.sh\n> index 3fbbc53..dfb71a1 100755\n> --- a/contrib/ciabot/ciabot.sh\n> +++ b/contrib/ciabot/ciabot.sh\n> @@ -39,7 +39,7 @@\n>  #       done\n>  #\n>  # The reason for the tac call is that git rev-list emits commits from\n> -# most recent to least - better to ship notifactions from oldest to newest.\n> +# most recent to least - better to ship notifications from oldest to newest.\n>  #\n>  # Configuration variables affecting this script:\n>  #\n> @@ -64,7 +64,7 @@\n>  # down. It is unknown whether this is still an issue in 2010, but\n>  # XML-RPC would be annoying to do from sh in any case. (XML-RPC does\n>  # have the advantage that it guarantees notification of multiple commits\n> -# shpped from an update in their actual order.)\n> +# shipped from an update in their actual order.)\n>  #\n>  \n>  # The project as known to CIA. You can set this with a -p option,\n> diff --git a/contrib/subtree/git-subtree.txt b/contrib/subtree/git-subtree.txt\n> index 7ba853e..e0957ee 100644\n> --- a/contrib/subtree/git-subtree.txt\n> +++ b/contrib/subtree/git-subtree.txt\n> @@ -270,7 +270,7 @@ git-extensions repository in ~/git-extensions/:\n>  name\n>  \n>  You can omit the --squash flag, but doing so will increase the number\n> -of commits that are incldued in your local repository.\n> +of commits that are included in your local repository.\n>  \n>  We now have a ~/git-extensions/git-subtree directory containing code\n>  from the master branch of git://github.com/apenwarr/git-subtree.git\n> diff --git a/git-mergetool--lib.sh b/git-mergetool--lib.sh\n> index e338be5..7e5c525 100644\n> --- a/git-mergetool--lib.sh\n> +++ b/git-mergetool--lib.sh\n> @@ -117,7 +117,7 @@ valid_tool () {\n>  setup_tool () {\n>  \ttool=\"$1\"\n>  \n> -\t# Fallback definitions, to be overriden by tools.\n> +\t# Fallback definitions, to be overridden by tools.\n>  \tcan_merge () {\n>  \t\treturn 0\n>  \t}\n> diff --git a/git-p4.py b/git-p4.py\n> index 88fcf23..31e71ff 100755\n> --- a/git-p4.py\n> +++ b/git-p4.py\n> @@ -1786,7 +1786,7 @@ class P4Submit(Command, P4UserMap):\n>              missingGitTags = gitTags - p4Labels\n>              self.exportGitTags(missingGitTags)\n>  \n> -        # exit with error unless everything applied perfecly\n> +        # exit with error unless everything applied perfectly\n>          if len(commits) != len(applied):\n>                  sys.exit(1)\n>  \n> diff --git a/notes.h b/notes.h\n> index 3324c48..2a3f923 100644\n> --- a/notes.h\n> +++ b/notes.h\n> @@ -77,7 +77,7 @@ const char *default_notes_ref(void);\n>   * variable is used, and if that is missing, the default notes ref is used\n>   * (\"refs/notes/commits\").\n>   *\n> - * If you need to re-intialize a notes_tree structure (e.g. when switching from\n> + * If you need to re-initialize a notes_tree structure (e.g. when switching from\n>   * one notes ref to another), you must first de-initialize the notes_tree\n>   * structure by calling free_notes(struct notes_tree *).\n>   *\n> diff --git a/read-cache.c b/read-cache.c\n> index d97e3bf..fe7da6c 100644\n> --- a/read-cache.c\n> +++ b/read-cache.c\n> @@ -472,7 +472,7 @@ int remove_index_entry_at(struct index_state *istate, int pos)\n>  }\n>  \n>  /*\n> - * Remove all cache ententries marked for removal, that is where\n> + * Remove all cache entries marked for removal, that is where\n>   * CE_REMOVE is set in ce_flags.  This is much more effective than\n>   * calling remove_index_entry_at() for each entry to be removed.\n>   */\n> @@ -1743,7 +1743,7 @@ static int has_racy_timestamp(struct index_state *istate)\n>  }\n>  \n>  /*\n> - * Opportunisticly update the index but do not complain if we can't\n> + * Opportunistically update the index but do not complain if we can't\n>   */\n>  void update_index_if_able(struct index_state *istate, struct lock_file *lockfile)\n>  {\n> diff --git a/t/gitweb-lib.sh b/t/gitweb-lib.sh\n> index ae2dc46..9e381e0 100644\n> --- a/t/gitweb-lib.sh\n> +++ b/t/gitweb-lib.sh\n> @@ -36,7 +36,7 @@ EOF\n>  \n>  \t# You can set the GITWEB_TEST_INSTALLED environment variable to\n>  \t# the gitwebdir (the directory where gitweb is installed / deployed to)\n> -\t# of an existing gitweb instalation to test that installation,\n> +\t# of an existing gitweb installation to test that installation,\n>  \t# or simply to pathname of installed gitweb script.\n>  \tif test -n \"$GITWEB_TEST_INSTALLED\" ; then\n>  \t\tif test -d $GITWEB_TEST_INSTALLED; then\n> diff --git a/t/lib-t6000.sh b/t/lib-t6000.sh\n> index ea25dd8..4a397e6 100644\n> --- a/t/lib-t6000.sh\n> +++ b/t/lib-t6000.sh\n> @@ -37,7 +37,7 @@ save_tag()\n>  \tmv sed.script.tmp sed.script\n>  }\n>  \n> -# Replace unhelpful sha1 hashses with their symbolic equivalents\n> +# Replace unhelpful sha1 hashes with their symbolic equivalents\n>  entag()\n>  {\n>  \tsed -f sed.script\n> diff --git a/t/t7601-merge-pull-config.sh b/t/t7601-merge-pull-config.sh\n> index 25dac79..830a4c3 100755\n> --- a/t/t7601-merge-pull-config.sh\n> +++ b/t/t7601-merge-pull-config.sh\n> @@ -109,7 +109,7 @@ test_expect_success 'setup conflicted merge' '\n>  '\n>  \n>  # First do the merge with resolve and recursive then verify that\n> -# recusive is chosen.\n> +# recursive is chosen.\n>  \n>  test_expect_success 'merge picks up the best result' '\n>  \tgit config --unset-all pull.twohead &&\n> diff --git a/t/t9020-remote-svn.sh b/t/t9020-remote-svn.sh\n> index d9f6b73..4d81ba1 100755\n> --- a/t/t9020-remote-svn.sh\n> +++ b/t/t9020-remote-svn.sh\n> @@ -24,7 +24,7 @@ init_git () {\n>  \trm -fr .git &&\n>  \tgit init &&\n>  \t#git remote add svnsim testsvn::sim:///$TEST_DIRECTORY/t9020/example.svnrdump\n> -\t# let's reuse an exisiting dump file!?\n> +\t# let's reuse an existing dump file!?\n>  \tgit remote add svnsim testsvn::sim://$TEST_DIRECTORY/t9154/svn.dump\n>  \tgit remote add svnfile testsvn::file://$TEST_DIRECTORY/t9154/svn.dump\n>  }\n> diff --git a/t/t9112-git-svn-md5less-file.sh b/t/t9112-git-svn-md5less-file.sh\n> index a61d671..9861c71 100755\n> --- a/t/t9112-git-svn-md5less-file.sh\n> +++ b/t/t9112-git-svn-md5less-file.sh\n> @@ -7,7 +7,7 @@ test_description='test that git handles an svn repository with missing md5sums'\n>  # Loading a node from a svn dumpfile without a Text-Content-Length\n>  # field causes svn to neglect to store or report an md5sum.  (it will\n>  # calculate one if you had put Text-Content-Length: 0).  This showed\n> -# up in a repository creted with cvs2svn.\n> +# up in a repository created with cvs2svn.\n>  \n>  cat > dumpfile.svn <<EOF\n>  SVN-fs-dump-format-version: 1\n> diff --git a/t/t9802-git-p4-filetype.sh b/t/t9802-git-p4-filetype.sh\n> index eeefa67..87f4968 100755\n> --- a/t/t9802-git-p4-filetype.sh\n> +++ b/t/t9802-git-p4-filetype.sh\n> @@ -28,7 +28,7 @@ test_expect_success 'p4 client newlines, unix' '\n>  \t\ttest_cmp f-unix-orig f-unix &&\n>  \n>  \t\t# make sure stored in repo as unix newlines\n> -\t\t# use sed to eat python-appened newline\n> +\t\t# use sed to eat python-appended newline\n>  \t\tp4 -G print //depot/f-unix | marshal_dump data 2 |\\\n>  \t\t    sed \\$d >f-unix-p4-print &&\n>  \t\ttest_cmp f-unix-orig f-unix-p4-print &&\n> diff --git a/transport-helper.c b/transport-helper.c\n> index 522d791..2ba3012 100644\n> --- a/transport-helper.c\n> +++ b/transport-helper.c\n> @@ -1104,7 +1104,7 @@ static void *udt_copy_task_routine(void *udt)\n>  #ifndef NO_PTHREADS\n>  \n>  /*\n> - * Join thread, with apporiate errors on failure. Name is name for the\n> + * Join thread, with appropriate errors on failure. Name is name for the\n>   * thread (for error messages). Returns 0 on success, 1 on failure.\n>   */\n>  static int tloop_join(pthread_t thread, const char *name)\n> @@ -1170,7 +1170,7 @@ static void udt_kill_transfer(struct unidirectional_transfer *t)\n>  }\n>  \n>  /*\n> - * Join process, with apporiate errors on failure. Name is name for the\n> + * Join process, with appropriate errors on failure. Name is name for the\n>   * process (for error messages). Returns 0 on success, 1 on failure.\n>   */\n>  static int tloop_join(pid_t pid, const char *name)\n> --\n\nEyeballed-by: Stefan Beller <stefanbeller@googlemail.com>\n\n"},{"id":"224253","messageId":"51F6B610.70906@xiplink.com","threadId":"34558","inReplyTo":"7vk3k91cfy.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] More typofixes.","fromName":"Marc Branchaud","fromEmail":"marcnarc@xiplink.com","sentAt":"2013-07-29T18:36:00Z","receivedAt":"2013-07-29T18:36:00Z","isPatch":true,"sender":{"key":"marcnarc@xiplink.com","avatar":"https://avatars.githubusercontent.com/u/14980203?v=4"},"body":"On 13-07-29 01:52 PM, Junio C Hamano wrote:\n> Here is what I salvaged for 'maint'.  Eyeballing by others is very\n> much appreciated.\n> \n> -- >8 --\n> From: Ondřej Bílka <neleai@seznam.cz>\n> Subject: [PATCH] many small typofixes\n> Date: Mon, 29 Jul 2013 10:18:21 +0200\n> \n> Signed-off-by: Ondřej Bílka <neleai@seznam.cz>\n> Signed-off-by: Junio C Hamano <gitster@pobox.com>\n\nLooks good.\n\nReviewed-by: Marc Branchaud <marcnarc@xiplink.com>\n\n\t\tM.\n"},{"id":"224255","messageId":"7vvc3tyxfu.fsf@alter.siamese.dyndns.org","threadId":"34558","inReplyTo":"51F6B610.70906@xiplink.com","subject":"Re: [PATCH] More typofixes.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-07-29T19:32:05Z","receivedAt":"2013-07-29T19:32:05Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Marc Branchaud <marcnarc@xiplink.com> writes:\n\n> On 13-07-29 01:52 PM, Junio C Hamano wrote:\n>> Here is what I salvaged for 'maint'.  Eyeballing by others is very\n>> much appreciated.\n>> \n>> -- >8 --\n>> From: Ondřej Bílka <neleai@seznam.cz>\n>> Subject: [PATCH] many small typofixes\n>> Date: Mon, 29 Jul 2013 10:18:21 +0200\n>> \n>> Signed-off-by: Ondřej Bílka <neleai@seznam.cz>\n>> Signed-off-by: Junio C Hamano <gitster@pobox.com>\n>\n> Looks good.\n>\n> Reviewed-by: Marc Branchaud <marcnarc@xiplink.com>\n>\n> \t\tM.\n\nThanks.\n"}]}