summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 2482d7d)
raw | patch | inline | side by side (parent: 2482d7d)
author | Junio C Hamano <junkio@cox.net> | |
Sun, 16 Oct 2005 00:03:30 +0000 (17:03 -0700) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Sun, 16 Oct 2005 00:03:30 +0000 (17:03 -0700) |
Documentation/tutorial.txt | patch | blob | history |
index 6ecb089c5cc4cf8dcaa8005c0ee6e4208bced346..00f4bab954f9d40000593bdfa04145ca5504b680 100644 (file)
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
-the reference to the top-of-tree of the master branch, and since
-that's exactly what `git-commit-tree` spits out, we can do this
-all with a sequence of simple shell commands:
+And this is where we create the `.git/refs/heads/master` file. This file is
+supposed to contain the reference to the top-of-tree, and since that's
+exactly what `git-commit-tree` spits out, we can do this all with a simple
+shell pipeline:
------------------------------------------------
-tree=$(git-write-tree)
-commit=$(echo 'Initial commit' | git-commit-tree $tree)
-git-update-ref HEAD $(commit)
+echo "Initial commit" | \
+ git-commit-tree $(git-write-tree) > .git/refs/heads/master
------------------------------------------------
which will say: