From: "Jakub Narębski" <jnareb@gmail.com>
To: Olaf Hering <olaf@aepfle.de>, Fredrik Gustafsson <iveqy@iveqy.com>
Cc: git@vger.kernel.org
Subject: Re: how to reduce disk usage for large .git dirs?
Date: Fri, 14 Nov 2014 13:32:09 +0100 [thread overview]
Message-ID: <5465F649.4090906@gmail.com> (raw)
In-Reply-To: <20141113120313.GB15503@aepfle.de>
W dniu 2014-11-13 13:03, Olaf Hering pisze:
> On Thu, Nov 13, Fredrik Gustafsson wrote:
[...]
>> Your setup looks familiar to me for a subversion user switching to git
>> and trying to use git as subversion. The common usecase is not to have
>> multiple worktrees but to do a checkout to the worktree you need to work
>> on. This is possible with git since it's very fast and I recommend you
>> to try to use one worktree.
> Switching branches will invalidate timestamps, causing a full rebuild.
Wouldn't a better way of solving "full rebuild" issue be to use ccache
or similar solution?
Anyway, switching branches invalidates timestamps only on those files
that change between branches -- it is to avoid unnecessary rebuilds.
You can always clone with --reference, and use alternates (alternate
object store). Just don't delete objects in repository that other
repositories borrow from; GitHub uses refs/borrowers/ namespace for
that, IIRC.
HTH
--
Jakub Narębski
next prev parent reply other threads:[~2014-11-14 12:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 11:14 how to reduce disk usage for large .git dirs? Olaf Hering
2014-11-13 11:49 ` Fredrik Gustafsson
2014-11-13 12:03 ` Olaf Hering
2014-11-14 12:32 ` Jakub Narębski [this message]
2014-11-13 12:02 ` Roger Gammans
2014-11-13 12:21 ` Olaf Hering
2014-11-13 12:09 ` Duy Nguyen
2014-11-13 15:44 ` Olaf Hering
2014-11-13 16:03 ` Fredrik Gustafsson
2014-11-13 16:08 ` Johan Herland
2014-11-13 20:15 ` Jeff King
2014-11-14 10:14 ` Olaf Hering
2014-11-14 10:24 ` Fredrik Gustafsson
2014-11-14 10:30 ` Olaf Hering
2014-11-14 10:54 ` Olaf Hering
2014-11-14 11:24 ` Olaf Hering
2014-11-14 15:06 ` Andreas Schwab
2014-11-25 14:32 ` Olaf Hering
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=5465F649.4090906@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=iveqy@iveqy.com \
--cc=olaf@aepfle.de \
/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.