[PATCH 1/2] Documentation: remove --prune from...

[PATCH 1/2] Documentation: remove --prune from pack-refs examples

From: Jonathon Mah <hidden>
Date: 2016-06-15 22:58:12

The option has been the default for a while, and doesn't otherwise
appear in the page.
---
 Documentation/git-pack-refs.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/git-pack-refs.txt b/Documentation/git-pack-refs.txt
index f131677..154081f 100644
--- a/Documentation/git-pack-refs.txt
+++ b/Documentation/git-pack-refs.txt

@@ -33,8 +33,8 @@ Subsequent updates to branches always create new files under
 `$GIT_DIR/refs` directory hierarchy.
 
 A recommended practice to deal with a repository with too many
-refs is to pack its refs with `--all --prune` once, and
-occasionally run `git pack-refs --prune`.  Tags are by
+refs is to pack its refs with `--all` once, and
+occasionally run `git pack-refs`.  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,

-- 
1.8.3.3.754.g9c3c367




Jonathon Mah
me@JonathonMah.com

[PATCH 2/2] Documentation: fix git-prune example usage

From: Jonathon Mah <hidden>
Date: 2016-06-15 22:58:12

---
 Documentation/git-prune.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/git-prune.txt b/Documentation/git-prune.txt
index 80d01b0..bf82410 100644
--- a/Documentation/git-prune.txt
+++ b/Documentation/git-prune.txt

@@ -59,7 +59,7 @@ borrows from your repository via its
 `.git/objects/info/alternates`:
 
 ------------
-$ git prune $(cd ../another && $(git rev-parse --all))
+$ git prune $(cd ../another && git rev-parse --all)
 ------------
 
 Notes

-- 
1.8.3.3.754.g9c3c367



Jonathon Mah
me@JonathonMah.com

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help