Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
doc/git-pack-refs: fix two grammar issues
author
Markus Heidelberg
<markus.heidelberg@web.de>
Sat, 4 Apr 2009 10:35:22 +0000
(12:35 +0200)
committer
Junio C Hamano
<gitster@pobox.com>
Sun, 5 Apr 2009 07:39:37 +0000
(
00:39
-0700)
Signed-off-by: Markus Heidelberg <markus.heidelberg@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-pack-refs.txt
patch
|
blob
|
history
raw
|
patch
|
inline
| side by side (parent:
3346330
)
diff --git
a/Documentation/git-pack-refs.txt
b/Documentation/git-pack-refs.txt
index a5244d35f49f10b7954d8fa52164663e3d167d4b..1ee99c208ce4893d2fa2367544b22ed0c8b18044 100644
(file)
--- a/
Documentation/git-pack-refs.txt
+++ b/
Documentation/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.
traditional `$GIT_DIR/refs` hierarchy, it is looked up in this
file and used if found.
-Subsequent updates to branches always create
s 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
`$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,
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.
unpacked.