summaryrefslogtreecommitdiffstats
path: root/git-pack-refs.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@hera.kernel.org>2009-04-05 09:18:17 +0000
committerJunio C Hamano <junio@hera.kernel.org>2009-04-05 09:18:17 +0000
commita6499d7ec9607dc1c5a1d0ba7be250423250dcfe (patch)
tree9b7bab9259c7dde19f7058716dbbf381faef35ef /git-pack-refs.txt
parent3c523f4adab5f87c21997caf21275b1d586d4615 (diff)
downloadgit-htmldocs-a6499d7ec9607dc1c5a1d0ba7be250423250dcfe.tar.gz
Autogenerated HTML docs for v1.6.2.2-414-g81aa
Diffstat (limited to 'git-pack-refs.txt')
-rw-r--r--git-pack-refs.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/git-pack-refs.txt b/git-pack-refs.txt
index a5244d35f..1ee99c208 100644
--- a/git-pack-refs.txt
+++ b/git-pack-refs.txt
@@ -26,7 +26,7 @@ problem by stashing the refs in a single file,
traditional `$GIT_DIR/refs` hierarchy, it is looked up in this
file and used if found.
-Subsequent updates to branches always creates new file under
+Subsequent updates to branches always create new files under
`$GIT_DIR/refs` hierarchy.
A recommended practice to deal with a repository with too many
@@ -35,7 +35,7 @@ occasionally run `git pack-refs \--prune`. Tags are by
definition stationary and are not expected to change. Branch
heads will be packed with the initial `pack-refs --all`, but
only the currently active branch heads will become unpacked,
-and next `pack-refs` (without `--all`) will leave them
+and the next `pack-refs` (without `--all`) will leave them
unpacked.