summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuiz Fernando N. Capitulino <lcapitulino@mandriva.com.br>2007-04-25 14:18:28 (GMT)
committerJunio C Hamano <junkio@cox.net>2007-04-25 20:44:45 (GMT)
commit79dbbedd78ae064be6bb8a0f61fd4872222e47dd (patch)
treeb9cd13bd160d13efdbddb3c9cdbfc59a994ae5a5
parent3511a3774e60783d979ebc2ef7b04371a23602bb (diff)
downloadgit-79dbbedd78ae064be6bb8a0f61fd4872222e47dd.zip
git-79dbbedd78ae064be6bb8a0f61fd4872222e47dd.tar.gz
git-79dbbedd78ae064be6bb8a0f61fd4872222e47dd.tar.bz2
core-tutorial: minor fixes
- Do not break the line when it's not needed - s/Your/You Signed-off-by: Luiz Fernando N. Capitulino <lcapitulino@mandriva.com.br> Signed-off-by: Junio C Hamano <junkio@cox.net>
-rw-r--r--Documentation/core-tutorial.txt9
1 files changed, 4 insertions, 5 deletions
diff --git a/Documentation/core-tutorial.txt b/Documentation/core-tutorial.txt
index 97cdb90..6b9b9ad 100644
--- a/Documentation/core-tutorial.txt
+++ b/Documentation/core-tutorial.txt
@@ -319,10 +319,9 @@ argument to `git-commit-tree`.
`git-commit-tree` normally takes several arguments -- it wants to know
what the 'parent' of a commit was, but since this is the first commit
ever in this new repository, and it has no parents, we only need to pass in
-the object name of the tree. However, `git-commit-tree`
-also wants to get a commit message
-on its standard input, and it will write out the resulting object name for the
-commit to its standard output.
+the object name of the tree. However, `git-commit-tree` also wants to get a
+commit message on its standard input, and it will write out the resulting
+object name for the commit to its standard output.
And this is where we create the `.git/refs/heads/master` file
which is pointed at by `HEAD`. This file is supposed to contain
@@ -1304,7 +1303,7 @@ So, we can use somebody else's work from a remote repository, but
how can *you* prepare a repository to let other people pull from
it?
-Your do your real work in your working tree that has your
+You do your real work in your working tree that has your
primary repository hanging under it as its `.git` subdirectory.
You *could* make that repository accessible remotely and ask
people to pull from it, but in practice that is not the way