From: Peter Hagervall <hager@cs.umu.se>
To: torvalds@osdl.org
Cc: git@vger.kernel.org
Subject: [PATCH] Spelling fixes for git tutorial
Date: Thu, 2 Jun 2005 09:39:21 +0200 [thread overview]
Message-ID: <20050602073920.GA526@peppar.cs.umu.se> (raw)
Fix a few spellos in the otherwise excellent tutorial.
Signed-off-by: Peter Hagervall <hager@cs.umu.se>
diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
--- a/Documentation/tutorial.txt
+++ b/Documentation/tutorial.txt
@@ -405,7 +405,7 @@ can do
git log
which shows just the log messages, or if we want to see the log together
-whith the associated patches use the more complex (and much more
+with the associated patches use the more complex (and much more
powerful)
git-whatchanged -p --root
@@ -423,10 +423,10 @@ With that, you should now be having some
can explore on your own.
- Copoying archives
+ Copying archives
-----------------
-Git arhives are normally totally self-sufficient, and it's worth noting
+Git archives are normally totally self-sufficient, and it's worth noting
that unlike CVS, for example, there is no separate notion of
"repository" and "working tree". A git repository normally _is_ the
working tree, with the local git information hidden in the ".git"
@@ -486,7 +486,7 @@ actual core git files. Such a repository
repository.
To create your own local live copy of such a "raw" git repository, you'd
-first create your own subdirectory for the project, adn then copy the
+first create your own subdirectory for the project, and then copy the
raw repository contents into the ".git" directory. For example, to
create your own copy of the git repository, you'd do the following
@@ -512,7 +512,7 @@ older version of a checked out tree you
file first, to tell git-checkout-cache to _force_ overwriting of any old
files).
-You have now successfully copied somebody elses (mine) remote
+You have now successfully copied somebody else's (mine) remote
repository, and checked it out.
[ to be continued.. cvs2git, tagging versions, branches, merging.. ]
reply other threads:[~2005-06-02 7:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050602073920.GA526@peppar.cs.umu.se \
--to=hager@cs.umu.se \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).