From: Joshua Juran <jjuran@gmail.com>
To: Chandra Sukiman <tmcchandra@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Reduce number of changes to pack file.
Date: Mon, 28 Mar 2011 06:29:34 -0700 [thread overview]
Message-ID: <3400B460-E01F-477C-AB14-5593BBF39419@gmail.com> (raw)
In-Reply-To: <AANLkTimFKGrSCgBShtERaGfd=9y+=q-aHsN3u5Lvf52v@mail.gmail.com>
On Mar 27, 2011, at 8:33 PM, Chandra Sukiman wrote:
> I am using git with Dropbox (see
> http://stackoverflow.com/questions/1960799/using-gitdropbox-together-effectively)
> .
I don't see how this can end any way other than in pain.
> As the repository size is getting bigger, sometime during the git gc,
> it will create a huge .pack file (300 mb) which need to be uploaded
> and downloaded by everyone.
Thank you for making my point for me. :-)
> I tried to limit the size of the pack to 10m (pack.packSizeLimit =
> 10m), but when doing gc, what happens now is that most of the pack
> files will get re-arranged and modified. This will cause the same
> upload/download issue that I want to solve.
:-)
> Is there any way for git gc to reduce the number of file changed?
I'm going to answer a completely different question: "Where should I
host my Git repo?". The answer is, on (a) one of the free hosting
services like GitHub (if your project is public), (b) one of the pay
services (like GitHub), or (c) your own Unix server. I use (a) and (c).
You shouldn't be hosting a Git repository on a file-based
synchronization service. It's asking for trouble.
Josh
next prev parent reply other threads:[~2011-03-28 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikqaD7QPCCw86OgGvCHLz1ySu5CzQXoY2rAojxB@mail.gmail.com>
2011-03-28 3:33 ` Reduce number of changes to pack file Chandra Sukiman
2011-03-28 13:29 ` Joshua Juran [this message]
2011-03-28 13:40 ` Santi Béjar
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=3400B460-E01F-477C-AB14-5593BBF39419@gmail.com \
--to=jjuran@gmail.com \
--cc=git@vger.kernel.org \
--cc=tmcchandra@gmail.com \
/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).