{"thread":{"id":"805","subject":"[PATCH] Spelling fixes for git tutorial","startedAt":"2005-06-02T07:39:21Z","lastAt":"2005-06-02T07:39:21Z","messageCount":1,"participants":["Peter Hagervall"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"4403","messageId":"20050602073920.GA526@peppar.cs.umu.se","threadId":"805","inReplyTo":null,"subject":"[PATCH] Spelling fixes for git tutorial","fromName":"Peter Hagervall","fromEmail":"hager@cs.umu.se","sentAt":"2005-06-02T07:39:21Z","receivedAt":"2005-06-02T07:39:21Z","isPatch":true,"sender":{"key":"hager@cs.umu.se","avatar":null},"body":"Fix a few spellos in the otherwise excellent tutorial.\n\nSigned-off-by: Peter Hagervall <hager@cs.umu.se>\n\n\ndiff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt\n--- a/Documentation/tutorial.txt\n+++ b/Documentation/tutorial.txt\n@@ -405,7 +405,7 @@ can do\n \tgit log\n \n which shows just the log messages, or if we want to see the log together\n-whith the associated patches use the more complex (and much more\n+with the associated patches use the more complex (and much more\n powerful)\n \n \tgit-whatchanged -p --root\n@@ -423,10 +423,10 @@ With that, you should now be having some\n can explore on your own.\n \n \n-\tCopoying archives\n+\tCopying archives\n \t-----------------\n \n-Git arhives are normally totally self-sufficient, and it's worth noting\n+Git archives are normally totally self-sufficient, and it's worth noting\n that unlike CVS, for example, there is no separate notion of\n \"repository\" and \"working tree\".  A git repository normally _is_ the\n working tree, with the local git information hidden in the \".git\"\n@@ -486,7 +486,7 @@ actual core git files. Such a repository\n repository.\n \n To create your own local live copy of such a \"raw\" git repository, you'd\n-first create your own subdirectory for the project, adn then copy the\n+first create your own subdirectory for the project, and then copy the\n raw repository contents into the \".git\" directory. For example, to\n create your own copy of the git repository, you'd do the following\n \n@@ -512,7 +512,7 @@ older version of a checked out tree you \n file first, to tell git-checkout-cache to _force_ overwriting of any old\n files). \n \n-You have now successfully copied somebody elses (mine) remote\n+You have now successfully copied somebody else's (mine) remote\n repository, and checked it out. \n \n [ to be continued.. cvs2git, tagging versions, branches, merging.. ]\n"}]}