@matheusbsbs / matheus-bagliano / commits / 79dbbedd78
Fork 0

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>

Luiz Fernando N. Capitulino committed Apr 25, 2007 at 11:18 UTC 79dbbedd78ae064be6bb8a0f61fd4872222e47dd
1 file changed +4 -5
Documentation/core-tutorial.txt
+4 -5
@@ -319,10 +319,9 @@ argument to `git-commit-tree`.
319 `git-commit-tree` normally takes several arguments -- it wants to know
320 what the 'parent' of a commit was, but since this is the first commit
321 ever in this new repository, and it has no parents, we only need to pass in
322 -the object name of the tree. However, `git-commit-tree`
323 -also wants to get a commit message
324 -on its standard input, and it will write out the resulting object name for the
325 -commit to its standard output.
322 +the object name of the tree. However, `git-commit-tree` also wants to get a
323 +commit message on its standard input, and it will write out the resulting
324 +object name for the commit to its standard output.
325
326 And this is where we create the `.git/refs/heads/master` file
327 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
1303 how can *you* prepare a repository to let other people pull from
1304 it?
1305
1307 -Your do your real work in your working tree that has your
1306 +You do your real work in your working tree that has your
1307 primary repository hanging under it as its `.git` subdirectory.
1308 You *could* make that repository accessible remotely and ask
1309 people to pull from it, but in practice that is not the way