diff options
-rw-r--r-- | Documentation/everyday.txt | 4 | ||||
-rw-r--r-- | Documentation/git.txt | 17 |
2 files changed, 11 insertions, 10 deletions
diff --git a/Documentation/everyday.txt b/Documentation/everyday.txt index 3851a040f..5775cd28a 100644 --- a/Documentation/everyday.txt +++ b/Documentation/everyday.txt @@ -133,6 +133,6 @@ and maintain access to the repository by developers. * gitlink:git-shell[1] can be used as a 'restricted login shell' for shared central repository users. - * howto/update-hook-example has a good example of - managing a shared central repository. + * link:howto/update-hook-example.txt[update hook howto] has a + good example of managing a shared central repository. diff --git a/Documentation/git.txt b/Documentation/git.txt index fc11516de..45773db13 100644 --- a/Documentation/git.txt +++ b/Documentation/git.txt @@ -36,23 +36,24 @@ OPTIONS CORE GIT COMMANDS ----------------- Before reading this cover to cover, you may want to take a look -at the link:tutorial.html[tutorial] document. +at the link:tutorial.html[tutorial] document. If you are +migrating from CVS, link:cvs-migration.html[cvs migration] +document may be helpful after you finish the tutorial. The <<Discussion>> section below contains much useful definition and clarification info - read that first. After that, if you are interested in using git to manage (version control) -projects, read on commands listed in Porcelain-ish commands -section next. On the other hand, if you are writing your own -Porcelain, I suggest reading gitlink:git-update-index[1] and -gitlink:git-read-tree[1] first. - -If you are migrating from CVS, link:cvs-migration.html[cvs migration] -document may be helpful after you finish the tutorial. +projects, use link:everyday.html[Everyday GIT] as a guide to the +minimum set of commands you need to know for day-to-day work. After you get the general feel from the tutorial and this overview page, you may want to take a look at the link:howto-index.html[howto] documents. +If you are writing your own Porcelain, you need to be familiar +with most of the low level commands --- I suggest starting from +gitlink:git-update-index[1] and gitlink:git-read-tree[1]. + David Greaves <david@dgreaves.com> 08/05/05 |