threads / patch / 34466

v2, 2 partsDocumentation: remove --prune from pack-refs examples

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

## tl;dr

3 messages between Jul 18, 2013 and Jul 18, 2013. Diffs are folded; open one to read it.

replies: 2people: 2as markdown or json

Jonathon Mah· Jul 18, 2013, 16:53 UTC · lore

The option has been the default for a while, and doesn't otherwise appear in the page.

Signed-off-by: Jonathon Mah <me@JonathonMah.com>
---
Forgot sign-off in v1. Also, I was unsure whether to rewrap the lines (and if so, to how many columns); erred on the side of minimal changes.

 Documentation/git-pack-refs.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Show changes to Documentation/git-pack-refs.txt +2 −2

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

Jonathon Mah· Jul 18, 2013, 16:53 UTC · re: Jonathon Mah · lore

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

Signed-off-by: Jonathon Mah <me@JonathonMah.com>
---
 Documentation/git-prune.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Show changes to Documentation/git-prune.txt +1 −1

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

Junio C Hamano· Jul 18, 2013, 18:07 UTC · re: Jonathon Mah · lore

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

Jonathon Mah <me@JonathonMah.com> writes:

Show 9 quoted lines

> The option has been the default for a while, and doesn't otherwise
> appear in the page.
>
> Signed-off-by: Jonathon Mah <me@JonathonMah.com>
> ---
>
> Forgot sign-off in v1. Also, I was unsure whether to rewrap the
> lines (and if so, to how many columns); erred on the side of
> minimal changes.

Thanks.

Show 18 quoted lines

>  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,