From: Jonas Fonseca <fonseca@diku.dk>
To: Petr Baudis <pasky@ucw.cz>
Cc: git@vger.kernel.org
Subject: [PATCH 3/5] Generate Documentation/introduction.html from the README file
Date: Sat, 13 Aug 2005 18:26:33 +0200 [thread overview]
Message-ID: <20050813162633.GD968@diku.dk> (raw)
In-Reply-To: <20050813162352.GA968@diku.dk>
Convert section names to use AsciiDoc markup. Fix a typo and refer to the
cg-* manpages.
Signed-off-by: Jonas Fonseca <fonseca@diku.dk>
---
Documentation/Makefile | 5 ++++-
README | 36 ++++++++++++++++++++++++------------
2 files changed, 28 insertions(+), 13 deletions(-)
diff --git a/Documentation/Makefile b/Documentation/Makefile
--- a/Documentation/Makefile
+++ b/Documentation/Makefile
@@ -4,7 +4,7 @@ CG_SRC=$(filter-out $(CG_IGNORE), $(wild
MAN1_TXT=$(patsubst ../cg-%,cg-%.txt,$(CG_SRC))
MAN7_TXT=cogito.txt
-DOC_HTML=$(patsubst %.txt,%.html,$(MAN1_TXT) $(MAN7_TXT))
+DOC_HTML=$(patsubst %.txt,%.html,$(MAN1_TXT) $(MAN7_TXT)) introduction.html
DOC_MAN1=$(patsubst %.txt,%.1,$(MAN1_TXT))
DOC_MAN7=$(patsubst %.txt,%.7,$(MAN7_TXT))
@@ -54,6 +54,9 @@ clean:
.PRECIOUS: %.txt
+introduction.html: ../README
+ asciidoc -b xhtml11 -d article -f asciidoc.conf -o $@ $<
+
%.html : %.txt
asciidoc -b xhtml11 -d manpage -f asciidoc.conf $<
diff --git a/README b/README
--- a/README
+++ b/README
@@ -1,5 +1,5 @@
- The Cogito Version Control System
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+The Cogito Version Control System
+=================================
Cogito is a version control system layered on top of the git tree history
storage system. Note that you can MOSTLY use it in parallel of other GIT
@@ -13,7 +13,8 @@ We shall first describe some quick ways
over each available command one by one.
- Downloading Cogito From Scratch
+Downloading Cogito From Scratch
+-------------------------------
Cogito can be obtained as a tarball from
@@ -39,13 +40,15 @@ The following tools are optional but str
preferred over the BSD variants)
- Starting a Fresh GIT Repository
+Starting a Fresh GIT Repository
+-------------------------------
If you want to start your own project using Cogito, there are two basic ways
to do this. You may start a fresh repository with no files in it, or you may
take an existing directory tree and turn it into a GIT repository.
- Starting an Empty Repository
+Starting an Empty Repository
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To create a new repository with no files in it, cd into an empty directory,
and give the following command:
@@ -59,7 +62,8 @@ That's it! You're now in your own GIT re
directory. Go into it and look around, but don't change anything in there.
That's what Cogito commands are for.
- Turning an Existing Directory Into a Repository
+Turning an Existing Directory Into a Repository
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you have a directory full of files, you can easily turn this into a
GIT repository. In fact, it is virtually the same as starting an empty
@@ -73,9 +77,11 @@ editor, and you're good to go. All of th
directory are now part of a GIT archive.
- Accessing Someone Else's GIT Repository
+Accessing Someone Else's GIT Repository
+---------------------------------------
- Creating the Repository
+Creating the Repository
+~~~~~~~~~~~~~~~~~~~~~~~
If you want to get started tracking an outside GIT repository, you first
must have Cogito's executables on your $PATH. Next, you need the URL (or
@@ -114,7 +120,8 @@ When you get your prompt back, do an ls
directory.
- Tracking Others' Work
+Tracking Others' Work
+~~~~~~~~~~~~~~~~~~~~~
Of course, once you have cloned a repository, you don't just want to leave
it at that. The upstream sources are constantly being updated, and you want
@@ -170,7 +177,8 @@ since your cg-pull. The alternative and
the cg-merge command, which we shall describe later.
- Other Stuff
+Other Stuff
+~~~~~~~~~~~
If there are any changes, two IDs will be printed (I mean the line saying
"Tree change"). Pass those as parameters to cg-diff and you will get a diff
@@ -222,10 +230,11 @@ Note that we missed out a lot of stuff h
for merging (cg-merge), moving your tree to an older commit (cg-seek), etc.
- Getting Help
+Getting Help
+------------
Cogito commands come with their own helpful documentation. To get help on
-cg-update, for example, give this command:
+cg-pull, for example, give this command:
$ cg-pull --help
@@ -233,6 +242,9 @@ or, for the same information, try this:
$ cg-help cg-pull
+Additionally, the man pages for the individual commands can be used as a
+reference.
+
You can ask thoughtful questions and make suggestions on the GIT mailing list:
git@vger.kernel.org
--
Jonas Fonseca
next prev parent reply other threads:[~2005-08-13 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-13 16:23 [PATCHSET] Cogito documentation updates Jonas Fonseca
2005-08-13 16:25 ` [PATCH 1/5] Also install cg-*.txt files Jonas Fonseca
2005-08-13 16:25 ` [PATCH 2/5] Add SEE ALSO section to cogito(7) which mentions git(7) Jonas Fonseca
2005-08-13 16:26 ` Jonas Fonseca [this message]
2005-08-13 16:30 ` [PATCH 4/5] Add more AsciiDoc markup to the README file Jonas Fonseca
2005-08-13 16:31 ` [PATCH 5/5] Ignore patch backup files when finding cg-* manpage scripts Jonas Fonseca
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050813162633.GD968@diku.dk \
--to=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).