From: Stephen Boyd <bebarino@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, lists@informa.tiker.net,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCHv1+eps] git-repack.txt: Clarify implications of -a for dumb protocols
Date: Thu, 4 Jun 2009 12:46:23 -0700 [thread overview]
Message-ID: <780e0a6b0906041246k43d42af1xe623168c52ff7e4f@mail.gmail.com> (raw)
In-Reply-To: <1244115295-28688-1-git-send-email-git@drmicha.warpmail.net>
On Thu, Jun 4, 2009 at 4:34 AM, Michael J
Gruber<git@drmicha.warpmail.net> wrote:
> 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.
Instead of adding this, why don't we just remove the part about dumb
protocols? So just say that it's especially useful for private
development. Then, if we really want to keep this performance note
just add it after the paragraph in one of those "+" things (What are
those called?)
next prev parent reply other threads:[~2009-06-04 19:46 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 ` [PATCHv1+eps] git-repack.txt: " Michael J Gruber
2009-06-04 13:34 ` Andreas Klöckner
2009-06-04 19:46 ` Stephen Boyd [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=780e0a6b0906041246k43d42af1xe623168c52ff7e4f@mail.gmail.com \
--to=bebarino@gmail.com \
--cc=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.
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 NNTP newsgroup(s).