Re: Limiting disk usage
- From
Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
- Date
- Oct 29, 2013, 13:50 UTC
- Message-ID
- <CAA01Cso+yTzatiAaQahx5h2N0nnOON7FsnWNSYrN-pV=8qzn7g@mail.gmail.com>
- In-Reply-To
- <vpqob68ebcu.fsf@anie.imag.fr>
[resending as sent previous version as HTML, sorry about that]
On Tue, Oct 29, 2013 at 9:21 AM, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:
Show 12 quoted lines
> > Piotr Krukowiecki <piotr.krukowiecki@gmail.com> writes: > > > Hi, > > > > What can be done to limit amount of space occupied on clone and > > checkout? I know about shallow clone and sparse checkout, anything > > else? > > Sorry if I'm stating the obvious, but "git gc" is a good start. If you > did something wrong with your repo before, maybe "git gc --aggressive" > can help.
Yes, I put a lot of code into the repository. I know it is wrong from git POV ;) That's why I wrote about splitting repository into multiple smaller repositories, but AFAIK git is not very good at managing that too...
(Background: we're thinking about migrating svn repository into git. Currently there is one svn repository containing many related directories. They are branched/merged/tagged together. Often work is done on all/many of them, but there are some use cases where we need only some of them)
-- Piotr Krukowiecki