{"thread":{"id":"11268","subject":"[PATCH resending] Fix spelling mistakes in user manual","startedAt":"2007-12-13T04:36:21Z","lastAt":"2007-12-13T04:36:21Z","messageCount":1,"participants":["Shawn Bohrer"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"62980","messageId":"1197520581-23376-1-git-send-email-shawn.bohrer@gmail.com","threadId":"11268","inReplyTo":null,"subject":"[PATCH resending] Fix spelling mistakes in user manual","fromName":"Shawn Bohrer","fromEmail":"shawn.bohrer@gmail.com","sentAt":"2007-12-13T04:36:21Z","receivedAt":"2007-12-13T04:36:21Z","isPatch":true,"sender":{"key":"shawn.bohrer@gmail.com","avatar":"https://gravatar.com/avatar/6eb093ef7d276306d18366254e0c95ff6a5db58231ac7e82fe78c2800aaae1b6?d=mp&s=160"},"body":"Signed-off-by: Shawn Bohrer <shawn.bohrer@gmail.com>\n---\n\nNot sure if this got lost, but I haven't see it applied and figured I\nshould resend.\n\n Documentation/user-manual.txt |    6 +++---\n 1 files changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\nindex 93a47b4..f2b4206 100644\n--- a/Documentation/user-manual.txt\n+++ b/Documentation/user-manual.txt\n@@ -1994,7 +1994,7 @@ $ git push ssh://yourserver.com/~you/proj.git +master\n -------------------------------------------------\n \n Normally whenever a branch head in a public repository is modified, it\n-is modified to point to a descendent of the commit that it pointed to\n+is modified to point to a descendant of the commit that it pointed to\n before.  By forcing a push in this situation, you break that convention.\n (See <<problems-with-rewriting-history>>.)\n \n@@ -2921,7 +2921,7 @@ As you can see, a commit is defined by:\n - a tree: The SHA1 name of a tree object (as defined below), representing\n   the contents of a directory at a certain point in time.\n - parent(s): The SHA1 name of some number of commits which represent the\n-  immediately prevoius step(s) in the history of the project.  The\n+  immediately previous step(s) in the history of the project.  The\n   example above has one parent; merge commits may have more than\n   one.  A commit with no parents is called a \"root\" commit, and\n   represents the initial revision of a project.  Each project must have\n@@ -3242,7 +3242,7 @@ to replace them by hand.  Back up your repository before attempting this\n in case you corrupt things even more in the process.\n \n We'll assume that the problem is a single missing or corrupted blob,\n-which is sometimes a solveable problem.  (Recovering missing trees and\n+which is sometimes a solvable problem.  (Recovering missing trees and\n especially commits is *much* harder).\n \n Before starting, verify that there is corruption, and figure out where\n-- \n1.5.3.6\n"}]}