summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 3511a37)
raw | patch | inline | side by side (parent: 3511a37)
author | Luiz Fernando N. Capitulino <lcapitulino@mandriva.com.br> | |
Wed, 25 Apr 2007 14:18:28 +0000 (11:18 -0300) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Wed, 25 Apr 2007 20:44:45 +0000 (13:44 -0700) |
- 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>
- s/Your/You
Signed-off-by: Luiz Fernando N. Capitulino <lcapitulino@mandriva.com.br>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/core-tutorial.txt | patch | blob | history |
index 97cdb90cb4e5763a4d0cec1a0d01f5380b4e512f..6b9b9ad7d1083ee09955ddaf46db4fad1a37834b 100644 (file)
`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
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