From bb8fb05ed082c81af81f9eecf356f993e2ef83b7 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Tue, 30 May 2006 07:21:12 +0000 Subject: [PATCH] Autogenerated HTML docs for v1.3.3-g2186 --- core-tutorial.html | 6 +++--- core-tutorial.txt | 4 ++-- everyday.html | 8 ++++---- everyday.txt | 6 +++--- tutorial-2.html | 4 ++-- tutorial-2.txt | 2 +- tutorial.html | 13 ++++++++++--- tutorial.txt | 12 ++++++++++-- 8 files changed, 35 insertions(+), 20 deletions(-) diff --git a/core-tutorial.html b/core-tutorial.html index f240b6bc..d74b0c73 100644 --- a/core-tutorial.html +++ b/core-tutorial.html @@ -255,11 +255,11 @@ div.exampleblock-content { padding-left: 0.5em; } -A short git tutorial +A git core tutorial for developers

Introduction

@@ -2011,7 +2011,7 @@ to follow, not easier.

diff --git a/core-tutorial.txt b/core-tutorial.txt index d1360ecd..5a831adf 100644 --- a/core-tutorial.txt +++ b/core-tutorial.txt @@ -1,5 +1,5 @@ -A short git tutorial -==================== +A git core tutorial for developers +================================== Introduction ------------ diff --git a/everyday.html b/everyday.html index 5e768ab1..831183b4 100644 --- a/everyday.html +++ b/everyday.html @@ -342,7 +342,7 @@ repository health reasonably well.

  • check how many loose objects there are and how much -diskspace is wasted by not repacking. +disk space is wasted by not repacking.

  • @@ -381,7 +381,7 @@ and remove unneeded other packs

    Individual Developer (Standalone)

    A standalone individual developer does not exchange patches with -other poeple, and works alone in a single repository, using the +other people, and works alone in a single repository, using the following commands.

    • @@ -923,7 +923,7 @@ Run git-daemon to serve /pub/scm from inetd.
      -
      $ grep git /etc/inet.conf
+
      $ grep git /etc/inetd.conf
 git     stream  tcp     nowait  nobody \
   /usr/bin/git-daemon git-daemon --inetd --syslog --export-all /pub/scm
      @@ -1039,7 +1039,7 @@ upload to public HTTP server hosted by your ISP.
    diff --git a/everyday.txt b/everyday.txt index 4b563709..2ad2d613 100644 --- a/everyday.txt +++ b/everyday.txt @@ -66,7 +66,7 @@ $ git prune <4> <1> running without "--full" is usually cheap and assures the repository health reasonably well. <2> check how many loose objects there are and how much -diskspace is wasted by not repacking. +disk space is wasted by not repacking. <3> without "-a" repacks incrementally. repacking every 4-5MB of loose objects accumulation may be a good rule of thumb. <4> after repack, prune removes the duplicate loose objects. @@ -86,7 +86,7 @@ Individual Developer (Standalone)[[Individual Developer (Standalone)]] ---------------------------------------------------------------------- A standalone individual developer does not exchange patches with -other poeple, and works alone in a single repository, using the +other people, and works alone in a single repository, using the following commands. * gitlink:git-show-branch[1] to see where you are. @@ -370,7 +370,7 @@ Examples Run git-daemon to serve /pub/scm from inetd.:: + ------------ -$ grep git /etc/inet.conf +$ grep git /etc/inetd.conf git stream tcp nowait nobody \ /usr/bin/git-daemon git-daemon --inetd --syslog --export-all /pub/scm ------------ diff --git a/tutorial-2.html b/tutorial-2.html index a4640b22..afbe905a 100644 --- a/tutorial-2.html +++ b/tutorial-2.html @@ -622,7 +622,7 @@ pages for details.

    pages for any of the git commands; one good place to start would be with the commands mentioned in Everyday git. You should be able to find any unknown jargon in the -Glosssay.

    +Glossary.

    The CVS migration document explains how to import a CVS repository into git, and shows how to use git in a CVS-like way.

    @@ -634,7 +634,7 @@ example, creating a new commit.

    diff --git a/tutorial-2.txt b/tutorial-2.txt index 08d3453e..9c9500c1 100644 --- a/tutorial-2.txt +++ b/tutorial-2.txt @@ -377,7 +377,7 @@ At this point you should know everything necessary to read the man pages for any of the git commands; one good place to start would be with the commands mentioned in link:everyday.html[Everyday git]. You should be able to find any unknown jargon in the -link:glossary.html[Glosssay]. +link:glossary.html[Glossary]. The link:cvs-migration.html[CVS migration] document explains how to import a CVS repository into git, and shows how to use git in a diff --git a/tutorial.html b/tutorial.html index bdc6114f..88c3f92b 100644 --- a/tutorial.html +++ b/tutorial.html @@ -625,14 +625,21 @@ visualizing their history. For example,

    $ gitk --since="2 weeks ago" drivers/

    allows you to browse any commits from the last 2 weeks of commits -that modified files under the "drivers" directory.

    +that modified files under the "drivers" directory. (Note: you can +adjust gitk's fonts by holding down the control key while pressing +"-" or "+".)

    Finally, most commands that take filenames will optionally allow you to precede any filename by a commit, to specify a particular version -fo the file:

    +of the file:

    $ git diff v2.5:Makefile HEAD:Makefile.in
    +

    You can also use "git cat-file -p" to see any such file:

    +
    +
    +
    $ git cat-file -p v2.5:Makefile
    +

    Next Steps

    @@ -694,7 +701,7 @@ digressions that may be interesting at this point are:

    diff --git a/tutorial.txt b/tutorial.txt index 79781adf..039a8598 100644 --- a/tutorial.txt +++ b/tutorial.txt @@ -429,16 +429,24 @@ $ gitk --since="2 weeks ago" drivers/ ------------------------------------- allows you to browse any commits from the last 2 weeks of commits -that modified files under the "drivers" directory. +that modified files under the "drivers" directory. (Note: you can +adjust gitk's fonts by holding down the control key while pressing +"-" or "+".) Finally, most commands that take filenames will optionally allow you to precede any filename by a commit, to specify a particular version -fo the file: +of the file: ------------------------------------- $ git diff v2.5:Makefile HEAD:Makefile.in ------------------------------------- +You can also use "git cat-file -p" to see any such file: + +------------------------------------- +$ git cat-file -p v2.5:Makefile +------------------------------------- + Next Steps ---------- -- 2.11.0