From a11398a079f1a767bc4e99d57c6dd05da6181152 Mon Sep 17 00:00:00 2001
From: Ben Lynn <blynn@cs.stanford.edu>
Date: Tue, 11 Sep 2007 01:36:42 -0700
Subject: [PATCH] Added push target to Makefile

Minor edits and corrections
---
 Makefile     | 5 ++++-
 intro.txt    | 2 +-
 preface.html | 8 +++++++-
 3 files changed, 12 insertions(+), 3 deletions(-)

diff --git a/Makefile b/Makefile
index 698d966..1d83b59 100644
--- a/Makefile
+++ b/Makefile
@@ -1,4 +1,4 @@
-.PHONY: target clean sync
+.PHONY: target clean sync push
 
 target: book
 
@@ -27,5 +27,8 @@ book.pdf: book.xml
 clean:
 	-rm -rf book.xml book.html book
 
+push:
+	git-push blynn@git.or.cz:srv/git/gitmagic.git
+
 sync: target
 	rsync -r book/* blynn@tl1.stanford.edu:www/gitmagic/
diff --git a/intro.txt b/intro.txt
index bf7b612..6b43e9e 100644
--- a/intro.txt
+++ b/intro.txt
@@ -12,7 +12,7 @@ But this will overwrite the old version. It's like those old school games which
 
 == Version Control ==
 
-When editing, you can "Save As..." a different file, or copy the file somewhere first before saving if you want to savour old versions. Maybe compress them too to save space. This is version control, but very primitive and labour-intensive.Computer games improved on this out long ago, many of them allowing multiple automatically timestamped save slots.
+When editing, you can "Save As..." a different file, or copy the file somewhere first before saving if you want to savour old versions. Maybe compress them too to save space. This is version control, but very primitive and labour-intensive. Computer games improved on this long ago, many of them allowing multiple automatically timestamped save slots.
 
 Let's make the problem slightly tougher now. Say you have a bunch of files that go together, such as collection of source code for the same project, or files for a website. Now if you want to keep an old version you have to archive a whole directory of stuff. Keeping many versions around is inconvenient to do by hand, and gets expensive fast.
 
diff --git a/preface.html b/preface.html
index 98d3423..9891a23 100644
--- a/preface.html
+++ b/preface.html
@@ -41,7 +41,7 @@ Git versus Subversion: articles by
 <a href="http://subversion.tigris.org/subversion-linus.html">Subversion vs itself</a>: in response to its defence of Subversion's limitations, I claim Git is right for <i>every</i> project. I also claim where there is more than one programmer, there is decentralized development.
 </p>
 <p>
-Saying you should use systems that don't scale well when your project is small is like saying you should use Roman numerals for calculations involving small numbers.
+Saying you should use systems that don't scale well when your project is tiny is like saying you should use Roman numerals for calculations involving small numbers.
 </p>
     </li>
     <li>
@@ -72,3 +72,9 @@ Other guides:
 <a href="http://polywww.in2p3.fr/~gaycken/Calice/Software/my_git_workflow.html">Advanced Git work flow</a> described by Götz Gaycken.
     </li>
 </ul>
+<h2>Free Git Hosting</h2>
+<p>
+This guide is hosted by Git at <a href="http://repo.or.cz/">repo.or.cz</a>,
+who provide free Git hosting for free projects.
+See <a href="http://repo.or.cz/w/gitmagic.git">the Git-web summary of this guide</a>.
+</p>
-- 
2.11.4.GIT