All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Berov <vitaly.berov@gmail.com>
To: git@vger.kernel.org
Subject: Re: git clone: very long "resolving deltas" phase
Date: Sat, 10 Apr 2010 12:05:54 +0400	[thread overview]
Message-ID: <hppbhu$bc7$1@dough.gmane.org> (raw)
In-Reply-To: <vpqr5mp6o1q.fsf@bauges.imag.fr>

On 04/09/2010 12:13 PM, Matthieu Moy wrote:
> Vitaly Berov<vitaly.berov@gmail.com>  writes:
>
>> Objects amount: 3997548.
>> Size of the repository: ~57Gb.
> [...]
>> By the way, we have a large amount of binary files in our rep.
>
> This is clearly not the kind of repositories Git is good at.
Hmm.. I'm looking for a good repository because I'm tired of subversion, 
Perforce isn't an option to (very expensive and even more 
uncomfortable). It seems like there only Git/Mercurial are good options. 
Can you recommend some other scms?

> I encourage you to continue this discussion, and try to find a way to
> get it working, but the standard approach (probably a "my 2 cents"
> kind of advices, but ...) would be:
>
> * Split your repo into smaller ones (submodules ...)
>
> * Avoid versionning binary files

I can't get rid of binary files because they are the "sources" of our 
artists work (the develop a game).
Splitting a repo can be an option, but it's very inconvenient for us.

Vitaly

  parent reply	other threads:[~2010-04-10  8:06 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 14:18 git clone: very long "resolving deltas" phase Vitaly Berov
2010-04-06 15:01 ` Matthieu Moy
2010-04-06 15:28   ` Vitaly Berov
2010-04-06 15:29   ` Vitaly
2010-04-06 15:32     ` Andreas Ericsson
     [not found]       ` <q2mec874dac1004060850r5eaa41fak2ba9889d07794651@mail.gmail.com>
2010-04-06 15:56         ` Vitaly Berov
2010-04-06 21:09           ` Nicolas Pitre
2010-04-07  5:54             ` Vitaly Berov
2010-04-07  8:00               ` Ilari Liusvaara
2010-04-07  8:14                 ` Vitaly
2010-04-07  9:00                   ` Ilari Liusvaara
2010-04-07  9:37                   ` Jakub Narebski
2010-04-07 14:20                   ` Nicolas Pitre
2010-04-07 14:35                     ` Vitaly
2010-04-07 14:55                       ` Nicolas Pitre
2010-04-09  6:46                         ` Vitaly Berov
2010-04-09 19:30                           ` Nicolas Pitre
2010-04-10  6:32                             ` Vitaly Berov
2010-04-07 14:08                 ` Nicolas Pitre
2010-04-07 14:29                   ` Sverre Rabbelier
2010-04-07 14:37                     ` Vitaly
2010-04-07  5:55             ` Vitaly
2010-04-07 12:42               ` Nicolas Pitre
2010-04-06 21:05       ` Nicolas Pitre
2010-04-07  9:22         ` git clone: very long &quot;resolving deltas&quot; phase Marat Radchenko
2010-04-07 14:40           ` Nicolas Pitre
2010-04-06 21:01   ` git clone: very long "resolving deltas" phase Nicolas Pitre
2010-04-06 21:10 ` Nicolas Pitre
2010-04-07  5:57   ` Vitaly
2010-04-07 12:55     ` Nicolas Pitre
2010-04-09  6:50       ` Vitaly Berov
2010-04-09  8:13         ` Matthieu Moy
2010-04-09 19:18           ` Nicolas Pitre
2010-04-10  8:05           ` Vitaly Berov [this message]
2010-04-09 19:25         ` Nicolas Pitre
2010-04-10  7:58           ` Vitaly Berov
2010-04-10 13:25       ` Vitaly Berov
2010-04-11  0:50         ` Nicolas Pitre
2010-04-12 15:31           ` Vitaly

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='hppbhu$bc7$1@dough.gmane.org' \
    --to=vitaly.berov@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.