From 1c70883dc871f015b3f14945f7c310325ab4aba8 Mon Sep 17 00:00:00 2001
From: Junio C Hamano
Date: Fri, 2 Nov 2007 02:47:50 +0000
Subject: [PATCH] Autogenerated HTML docs for v1.5.3.5-474-g3e4bb
---
RelNotes-1.5.3.5.txt | 6 ------
git-clone.html | 8 ++++----
git-clone.txt | 6 +++---
git-filter-branch.html | 4 ++--
git-filter-branch.txt | 2 +-
git-format-patch.html | 4 ++--
git-format-patch.txt | 2 +-
git-mergetool.html | 9 +++++++--
git-mergetool.txt | 8 +++++++-
git.html | 2 +-
git.txt | 1 +
11 files changed, 29 insertions(+), 23 deletions(-)
diff --git a/RelNotes-1.5.3.5.txt b/RelNotes-1.5.3.5.txt
index bf6a279ed..4e46d2c2a 100644
--- a/RelNotes-1.5.3.5.txt
+++ b/RelNotes-1.5.3.5.txt
@@ -92,9 +92,3 @@ Fixes since v1.5.3.4
* "git-rebase -interactive" did not handle its "--strategy" option
properly.
-
---
-exec >/var/tmp/1
-O=v1.5.3.4-65-gf91333d
-echo O=`git describe refs/heads/maint`
-git shortlog --no-merges $O..refs/heads/maint
diff --git a/git-clone.html b/git-clone.html
index 24c834419..5305119f2 100644
--- a/git-clone.html
+++ b/git-clone.html
@@ -438,11 +438,11 @@ configuration variables.
Create a shallow clone with a history truncated to the
- specified number of revs. A shallow repository has
+ specified number of revisions. A shallow repository has a
number of limitations (you cannot clone or fetch from
it, nor push from nor into it), but is adequate if you
- want to only look at near the tip of a large project
- with a long history, and would want to send in a fixes
+ are only interested in the recent history of a large project
+ with a long history, and would want to send in fixes
as patches.
@@ -641,7 +641,7 @@ Create a repository on the kernel.org machine that borrows from Linus