{"thread":{"id":"15712","subject":"[PATCH] Typos.","startedAt":"2008-09-29T20:30:00Z","lastAt":"2008-09-29T20:30:00Z","messageCount":1,"participants":["Ralf Wildenhues"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"91879","messageId":"20080929202959.GD22976@ins.uni-bonn.de","threadId":"15712","inReplyTo":null,"subject":"[PATCH] Typos.","fromName":"Ralf Wildenhues","fromEmail":"ralf.wildenhues@gmx.de","sentAt":"2008-09-29T20:30:00Z","receivedAt":"2008-09-29T20:30:00Z","isPatch":true,"sender":{"key":"ralf.wildenhues@gmx.de","avatar":null},"body":"---\n Documentation/RelNotes-1.6.1.txt |    4 ++--\n Documentation/git-read-tree.txt  |    2 +-\n 2 files changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/RelNotes-1.6.1.txt b/Documentation/RelNotes-1.6.1.txt\nindex 421e569..906932c 100644\n--- a/Documentation/RelNotes-1.6.1.txt\n+++ b/Documentation/RelNotes-1.6.1.txt\n@@ -59,7 +59,7 @@ on.\n \n * \"git daemon\" learned --max-connections=<count> option.\n \n-* \"git diff\" learned to mimick --suppress-blank-empty from GNU diff via a\n+* \"git diff\" learned to mimic --suppress-blank-empty from GNU diff via a\n   configuration option.\n \n * \"git diff\" learned to put more sensible hunk headers for Python and\n@@ -121,7 +121,7 @@ release, unless otherwise noted.\n   is a path in it).\n \n * \"git diff --stdin\" used to take two trees on a line and compared them,\n-  but we droppped support for such a use case long time ago.  This has\n+  but we dropped support for such a use case long time ago.  This has\n   been resurrected.\n \n * \"git filter-branch\" failed to rewrite a tag name with slashes in it.\ndiff --git a/Documentation/git-read-tree.txt b/Documentation/git-read-tree.txt\nindex 309deac..7160fa1 100644\n--- a/Documentation/git-read-tree.txt\n+++ b/Documentation/git-read-tree.txt\n@@ -212,7 +212,7 @@ output after two-tree merge.\n \n Case #3 is slightly tricky and needs explanation.  The result from this\n rule logically should be to remove the path if the user staged the removal\n-of the path and then swiching to a new branch.  That however will prevent\n+of the path and then switching to a new branch.  That however will prevent\n the initial checkout from happening, so the rule is modified to use M (new\n tree) only when the contents of the index is empty.  Otherwise the removal\n of the path is kept as long as $H and $M are the same.\n-- \n1.6.0.1.309.g48068\n"}]}