{"thread":{"id":"11785","subject":"[PATCH] fix doc typos","startedAt":"2008-01-29T19:38:55Z","lastAt":"2008-01-31T19:55:57Z","messageCount":5,"participants":["Jim Meyering","Miklos Vajna","Jean-Luc Herren"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"66846","messageId":"87myqoxvzk.fsf@rho.meyering.net","threadId":"11785","inReplyTo":null,"subject":"[PATCH] fix doc typos","fromName":"Jim Meyering","fromEmail":"jim@meyering.net","sentAt":"2008-01-29T19:38:55Z","receivedAt":"2008-01-29T19:38:55Z","isPatch":true,"sender":{"key":"jim@meyering.net","avatar":"https://avatars.githubusercontent.com/u/710630?v=4"},"body":"\nSigned-off-by: Jim Meyering \n---\n Documentation/RelNotes-1.5.3.3.txt | 2 +-\n Documentation/git-config.txt | 2 +-\n Documentation/git-cvsserver.txt | 4 ++--\n Documentation/git-rev-parse.txt | 6 +++---\n Documentation/technical/racy-git.txt | 2 +-\n 5 files changed, 8 insertions(+), 8 deletions(-)\n\ndiff --git a/Documentation/RelNotes-1.5.3.3.txt b/Documentation/RelNotes-1.5.3.3.txt\nindex 2a7bfdd..d213846 100644\n--- a/Documentation/RelNotes-1.5.3.3.txt\n+++ b/Documentation/RelNotes-1.5.3.3.txt\n@@ -12,7 +12,7 @@ Fixes since v1.5.3.2\n * The default shell on some FreeBSD did not execute the\n argument parsing code correctly and made git unusable.\n\n- * git-svn incorrectly spawned pager even when the user user\n+ * git-svn incorrectly spawned pager even when the user\n explicitly asked not to.\n\n * sample post-receive hook overquoted the envelope sender\ndiff --git a/Documentation/git-config.txt b/Documentation/git-config.txt\nindex e4d0e47..fa16171 100644\n--- a/Documentation/git-config.txt\n+++ b/Documentation/git-config.txt\n@@ -130,7 +130,7 @@ See also <>.\n\n -z, --null::\n \tFor all options that output values and/or keys, always\n-\tend values with with the null character (instead of a\n+\tend values with the null character (instead of a\n \tnewline). Use newline instead as a delimiter between\n \tkey and value. This allows for secure parsing of the\n \toutput without getting confused e.g. by values that\ndiff --git a/Documentation/git-cvsserver.txt b/Documentation/git-cvsserver.txt\nindex d75e401..c831548 100644\n--- a/Documentation/git-cvsserver.txt\n+++ b/Documentation/git-cvsserver.txt\n@@ -204,7 +204,7 @@ about `DBI->connect()`.\n\n gitcvs.dbname::\n \tDatabase name. The exact meaning depends on the\n-\tused database driver, for SQLite this is a filename.\n+\tselected database driver, for SQLite this is a filename.\n \tSupports variable substitution (see below). May\n \tnot contain semicolons (`;`).\n \tDefault: '%Ggitcvs.%m.sqlite'\n@@ -215,7 +215,7 @@ gitcvs.dbdriver::\n \twith 'DBD::SQLite', reported to work with\n \t'DBD::Pg', and reported *not* to work with 'DBD::mysql'.\n \tPlease regard this as an experimental feature. May not\n-\tcontain double colons (`:`).\n+\tcontain colons (`:`).\n \tDefault: 'SQLite'\n\n gitcvs.dbuser::\ndiff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt\nindex 5d9c369..af98882 100644\n--- a/Documentation/git-rev-parse.txt\n+++ b/Documentation/git-rev-parse.txt\n@@ -229,13 +229,13 @@ blobs contained in a commit.\n * A colon, optionally followed by a stage number (0 to 3) and a\n colon, followed by a path; this names a blob object in the\n index at the given path. Missing stage number (and the colon\n- that follows it) names an stage 0 entry. During a merge, stage\n+ that follows it) names a stage 0 entry. During a merge, stage\n 1 is the common ancestor, stage 2 is the target branch's version\n (typically the current branch), and stage 3 is the version from\n the branch being merged.\n\n Here is an illustration, by Jon Loeliger. Both node B and C are\n-a commit parents of commit node A. Parent commits are ordered\n+commit parents of commit node A. Parent commits are ordered\n left-to-right.\n\n G H I J\n@@ -291,7 +291,7 @@ and its parent commits exists. `r1{caret}@` notation means all\n parents of `r1`. `r1{caret}!` includes commit `r1` but excludes\n its all parents.\n\n-Here are a handful examples:\n+Here are a handful of examples:\n\n D G H D\n D F G H I J D F\ndiff --git a/Documentation/technical/racy-git.txt b/Documentation/technical/racy-git.txt\nindex 5030d9f..6bdf034 100644\n--- a/Documentation/technical/racy-git.txt\n+++ b/Documentation/technical/racy-git.txt\n@@ -184,7 +184,7 @@ In a large project where raciness avoidance cost really matters,\n however, the initial computation of all object names in the\n index takes more than one second, and the index file is written\n out after all that happens. Therefore the timestamp of the\n-index file will be more than one seconds later than the the\n+index file will be more than one seconds later than the\n youngest file in the working tree. This means that in these\n cases there actually will not be any racily clean entry in\n the resulting index.\n--\n1.5.4.rc5.1.ge6bfe\n"},{"id":"66924","messageId":"20080130204357.GC4475@genesis.frugalware.org","threadId":"11785","inReplyTo":"87myqoxvzk.fsf@rho.meyering.net","subject":"Re: [PATCH] fix doc typos","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2008-01-30T20:43:57Z","receivedAt":"2008-01-30T20:43:57Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"On Tue, Jan 29, 2008 at 08:38:55PM +0100, Jim Meyering wrote:\n> Here is an illustration, by Jon Loeliger. Both node B and C are\n> -a commit parents of commit node A. Parent commits are ordered\n> +commit parents of commit node A. Parent commits are ordered\n\nwouldn't this be \"Both commit node B and C are parents of commit node A.\"?\n\n- VMiklos\n"},{"id":"66925","messageId":"87ir1brq10.fsf@rho.meyering.net","threadId":"11785","inReplyTo":"20080130204357.GC4475@genesis.frugalware.org","subject":"Re: [PATCH] fix doc typos","fromName":"Jim Meyering","fromEmail":"jim@meyering.net","sentAt":"2008-01-30T20:56:27Z","receivedAt":"2008-01-30T20:56:27Z","isPatch":true,"sender":{"key":"jim@meyering.net","avatar":"https://avatars.githubusercontent.com/u/710630?v=4"},"body":"Miklos Vajna wrote:\n> On Tue, Jan 29, 2008 at 08:38:55PM +0100, Jim Meyering wrote:\n>> Here is an illustration, by Jon Loeliger. Both node B and C are\n>> -a commit parents of commit node A. Parent commits are ordered\n>> +commit parents of commit node A. Parent commits are ordered\n>\n> wouldn't this be \"Both commit node B and C are parents of commit node A.\"?\n\nThat does sound better.\nWhile you're word-smithing, how about s/node B/nodes B/, too:\n\n \"Both commit nodes B and C are parents of commit node A.\"\n\nSend a patch.\n"},{"id":"66948","messageId":"47A12D0C.7030304@gmx.ch","threadId":"11785","inReplyTo":"87myqoxvzk.fsf@rho.meyering.net","subject":"[PATCH] Documentation: Fix typo","fromName":"Jean-Luc Herren","fromEmail":"jlh@gmx.ch","sentAt":"2008-01-31T02:06:04Z","receivedAt":"2008-01-31T02:06:04Z","isPatch":true,"sender":{"key":"jlh@gmx.ch","avatar":null},"body":"\nSigned-off-by: Jean-Luc Herren \n---\n\nBeside the obvious s/if/is/ typo, is it easier to read this way?\nIt might be my ears but \"is run\" sounds strange to me.\n\njlh\n\n Documentation/git-cvsserver.txt | 2 +-\n 1 files changed, 1 insertions(+), 1 deletions(-)\n\ndiff --git a/Documentation/git-cvsserver.txt b/Documentation/git-cvsserver.txt\nindex c831548..d3e9993 100644\n--- a/Documentation/git-cvsserver.txt\n+++ b/Documentation/git-cvsserver.txt\n@@ -183,7 +183,7 @@ access method and requested operation.\n That means that even if you offer only read access (e.g. by using\n the pserver method), git-cvsserver should have write access to\n the database to work reliably (otherwise you need to make sure\n-that the database if up-to-date all the time git-cvsserver is run).\n+that the database is up-to-date any time git-cvsserver is executed).\n \n By default it uses SQLite databases in the git directory, named\n `gitcvs..sqlite`. Note that the SQLite backend creates\n-- \n1.5.3.8\n"},{"id":"66993","messageId":"20080131195557.GB25954@genesis.frugalware.org","threadId":"11785","inReplyTo":"87ir1brq10.fsf@rho.meyering.net","subject":"[PATCH] git rev-parse manpage: spelling fix","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2008-01-31T19:55:57Z","receivedAt":"2008-01-31T19:55:57Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"Signed-off-by: Miklos Vajna \n---\n\nOn Wed, Jan 30, 2008 at 09:56:27PM +0100, Jim Meyering wrote:\n> Send a patch.\n\nhere it is.\n\n Documentation/git-rev-parse.txt | 4 ++--\n 1 files changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt\nindex af98882..f02f6bb 100644\n--- a/Documentation/git-rev-parse.txt\n+++ b/Documentation/git-rev-parse.txt\n@@ -234,8 +234,8 @@ blobs contained in a commit.\n (typically the current branch), and stage 3 is the version from\n the branch being merged.\n \n-Here is an illustration, by Jon Loeliger. Both node B and C are\n-commit parents of commit node A. Parent commits are ordered\n+Here is an illustration, by Jon Loeliger. Both commit nodes B\n+and C are parents of commit node A. Parent commits are ordered\n left-to-right.\n \n G H I J\n-- \n1.5.4.rc5-dirty\n"}]}