From: Robert Clausecker <fuzxxl@gmail.com>
To: git@vger.kernel.org
Subject: Recommended packing for HTTP repositories
Date: Wed, 13 Feb 2013 13:38:42 +0100 [thread overview]
Message-ID: <1360759122.6610.15.camel@t520> (raw)
Hello!
I provide dumb HTTP access to a git repository on a server where I can't
enable the smart HTTP protocol. When the history of the repository
grows, should I run git repack to pack all revisions together? Would
that cause clients that just want to download a few commit to download
the whole pack? What is recommended to do?
Yours, Robert Clausecker
reply other threads:[~2013-02-13 12:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1360759122.6610.15.camel@t520 \
--to=fuzxxl@gmail.com \
--cc=git@vger.kernel.org \
/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).