From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Cc: lists@informa.tiker.net, Junio C Hamano <gitster@pobox.com>
Subject: [PATCHv1+eps] git-repack.txt: Clarify implications of -a for dumb protocols
Date: Thu, 4 Jun 2009 13:34:55 +0200 [thread overview]
Message-ID: <1244115295-28688-1-git-send-email-git@drmicha.warpmail.net> (raw)
In-Reply-To: <200906031950.56974.lists@informa.tiker.net>
The current text makes some users feel uneasy, worrying whether
'-a' could lead to corrupt repositories. Clarify that '-a'
may lead to performance issues only for dumb protocols.
Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
---
Is that clear enough but concise?
Applies to maint.
[Sorry for the resend, I managed to mistype the subject.]
Documentation/git-repack.txt | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-repack.txt b/Documentation/git-repack.txt
index aaa8852..8af5505 100644
--- a/Documentation/git-repack.txt
+++ b/Documentation/git-repack.txt
@@ -32,7 +32,10 @@ OPTIONS
pack everything referenced into a single pack.
Especially useful when packing a repository that is used
for private development and there is no need to worry
- about people fetching via dumb protocols from it. Use
+ about people fetching via dumb protocols from it.
+ (Over dumb protocols, one would have to fetch the whole new
+ pack in order to get any contained object, no matter how
+ many other objects in that pack exist locally already.) Use
with '-d'. This will clean up the objects that `git prune`
leaves behind, but `git fsck --full` shows as
dangling.
--
1.6.3.1.268.g94d6d1
next prev parent reply other threads:[~2009-06-04 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 23:50 git repack and dumb protocols Andreas Klöckner
2009-06-04 10:58 ` [PATCH] git-pack.txt: Clarify implications of -a for " Michael J Gruber
2009-06-04 11:34 ` Michael J Gruber [this message]
2009-06-04 13:34 ` [PATCHv1+eps] git-repack.txt: " Andreas Klöckner
2009-06-04 19:46 ` Stephen Boyd
2009-06-05 8:16 ` Michael J Gruber
2009-06-05 19:14 ` Stephen Boyd
2009-06-09 16:15 ` [PATCH] " Michael J Gruber
2009-06-04 12:47 ` git repack and " Peter Harris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1244115295-28688-1-git-send-email-git@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=lists@informa.tiker.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).