# [PATCH v2 1/2] Documentation: remove --prune from pack-refs examples 3 messages from 2013-07-18 to 2013-07-18. Participants: Jonathon Mah, Junio C Hamano. Thread: https://gitlist.dev/t/34466 ## Jonathon Mah, 2013-07-18 16:53 Subject: [PATCH v2 1/2] Documentation: remove --prune from pack-refs examples Message-ID: <0A7070DB-118A-44B2-A554-246459D0CEF3@JonathonMah.com> URL: https://gitlist.dev/e/0A7070DB-118A-44B2-A554-246459D0CEF3%40JonathonMah.com ``` The option has been the default for a while, and doesn't otherwise appear in the page. Signed-off-by: Jonathon Mah --- 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(-) 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, 2013-07-18 16:53 Subject: [PATCH v2 2/2] Documentation: fix git-prune example usage Message-ID: <707B830A-C628-432A-9B89-2D39EA2927CC@JonathonMah.com> URL: https://gitlist.dev/e/707B830A-C628-432A-9B89-2D39EA2927CC%40JonathonMah.com In-Reply-To: <0A7070DB-118A-44B2-A554-246459D0CEF3@JonathonMah.com> ``` Signed-off-by: Jonathon Mah --- 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 ``` ## Junio C Hamano, 2013-07-18 18:07 Subject: Re: [PATCH v2 1/2] Documentation: remove --prune from pack-refs examples Message-ID: <7vehav3fom.fsf@alter.siamese.dyndns.org> URL: https://gitlist.dev/e/7vehav3fom.fsf%40alter.siamese.dyndns.org In-Reply-To: <0A7070DB-118A-44B2-A554-246459D0CEF3@JonathonMah.com> ``` Jonathon Mah writes: > The option has been the default for a while, and doesn't otherwise > appear in the page. > > Signed-off-by: Jonathon Mah > --- > > 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. > 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, ```