mirrors/git
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

core-tutorial: minor fixes

Browse Source 
- 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>
This commit is contained in:
Luiz Fernando N. Capitulino
2007-04-25 11:18:28 -03:00
committed by Junio C Hamano
parent 3511a3774e
commit 79dbbedd78
1 changed files with 4 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
Documentation/core-tutorial.txt
View File

@ -319,10 +319,9 @@ argument to `git-commit-tree`.
`git-commit-tree` normally takes several arguments -- it wants to know `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 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 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` the object name of the tree. However, `git-commit-tree` also wants to get a
also wants to get a commit message commit message on its standard input, and it will write out the resulting
on its standard input, and it will write out the resulting object name for the object name for the commit to its standard output.
commit to its standard output.
And this is where we create the `.git/refs/heads/master` file And this is where we create the `.git/refs/heads/master` file
which is pointed at by `HEAD`. This file is supposed to contain 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 how can *you* prepare a repository to let other people pull from
it? 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. primary repository hanging under it as its `.git` subdirectory.
You *could* make that repository accessible remotely and ask You *could* make that repository accessible remotely and ask
people to pull from it, but in practice that is not the way people to pull from it, but in practice that is not the way