@matheusbsbs / matheus-bagliano / commits / 8b15e2fbc9
Fork 0

Link Everyday GIT to main documentation tree.

Signed-off-by: Junio C Hamano <junkio@cox.net>

Junio C Hamano committed Dec 9, 2005 at 23:41 UTC 8b15e2fbc9d9b9d04c70fe590a3d0562d4334c38
2 files changed +11 -10
Documentation/everyday.txt
+2 -2
@@ -133,6 +133,6 @@ and maintain access to the repository by developers.
133 * gitlink:git-shell[1] can be used as a 'restricted login shell'
134 for shared central repository users.
135
136 - * howto/update-hook-example has a good example of
137 - managing a shared central repository.
136 + * link:howto/update-hook-example.txt[update hook howto] has a
137 + good example of managing a shared central repository.
138
Documentation/git.txt
+9 -8
@@ -36,23 +36,24 @@ OPTIONS
36 CORE GIT COMMANDS
37 -----------------
38 Before reading this cover to cover, you may want to take a look
39 -at the link:tutorial.html[tutorial] document.
39 +at the link:tutorial.html[tutorial] document. If you are
40 +migrating from CVS, link:cvs-migration.html[cvs migration]
41 +document may be helpful after you finish the tutorial.
42
43 The <<Discussion>> section below contains much useful definition
44 and clarification info - read that first. After that, if you
45 are interested in using git to manage (version control)
44 -projects, read on commands listed in Porcelain-ish commands
45 -section next. On the other hand, if you are writing your own
46 -Porcelain, I suggest reading gitlink:git-update-index[1] and
47 -gitlink:git-read-tree[1] first.
48 -
49 -If you are migrating from CVS, link:cvs-migration.html[cvs migration]
50 -document may be helpful after you finish the tutorial.
46 +projects, use link:everyday.html[Everyday GIT] as a guide to the
47 +minimum set of commands you need to know for day-to-day work.
48
49 After you get the general feel from the tutorial and this
50 overview page, you may want to take a look at the
51 link:howto-index.html[howto] documents.
52
53 +If you are writing your own Porcelain, you need to be familiar
54 +with most of the low level commands --- I suggest starting from
55 +gitlink:git-update-index[1] and gitlink:git-read-tree[1].
56 +
57
58 David Greaves <david@dgreaves.com>
59 08/05/05