From: Sitaram Chamarty <sitaramc@gmail.com>
To: Enrico Weigelt <enrico.weigelt@vnc.biz>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
Andrew Ardill <andrew.ardill@gmail.com>,
Javier Domingo <javierdo1@gmail.com>,
git@vger.kernel.org
Subject: Re: Local clones aka forks disk size optimization
Date: Sun, 18 Nov 2012 16:12:06 +0530 [thread overview]
Message-ID: <CAMK1S_hCk3QdDn8XnXVisL1i2V0iPCZBYN989JmZ3JYr7ckRrA@mail.gmail.com> (raw)
In-Reply-To: <ccb8680a-97ad-4cf8-95d0-5e21f60494f4@zcs>
On Fri, Nov 16, 2012 at 11:34 PM, Enrico Weigelt <enrico.weigelt@vnc.biz> wrote:
>
>> Provide one "main" clone which is bare, pulls automatically, and is
>> there to stay (no pruning), so that all others can use that as a
>> reliable alternates source.
>
> The problem here, IMHO, is the assumption, that the main repo will
> never be cleaned up. But what to do if you dont wanna let it grow
> forever ?
That's not the only problem. I believe you only get the savings when
the main repo gets the commits first. Which is probably ok most of
the time but it's worth mentioning.
>
> hmm, distributed GC is a tricky problem.
Except for one little issue (see other thread, subject line "cloning a
namespace downloads all the objects"), namespaces appear to do
everything we want in terms of the typical use cases for alternates,
and/or 'git clone -l', at least on the server side.
next prev parent reply other threads:[~2012-11-18 10:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALZVapmG+HL0SQx8zx=Cfz5pWv84hJq90x-7VdjA0m2Z4dC34A@mail.gmail.com>
2012-11-14 23:42 ` Fwd: Local clones aka forks disk size optimization Javier Domingo
2012-11-15 0:18 ` Andrew Ardill
2012-11-15 0:40 ` Javier Domingo
2012-11-15 0:53 ` Andrew Ardill
2012-11-15 1:15 ` Javier Domingo
2012-11-15 1:34 ` Andrew Ardill
2012-11-15 3:44 ` Sitaram Chamarty
2012-11-16 11:25 ` Michael J Gruber
2012-11-16 18:04 ` Enrico Weigelt
2012-11-18 10:42 ` Sitaram Chamarty [this message]
2012-11-18 17:02 ` Enrico Weigelt
2012-11-16 14:55 ` Pyeron, Jason J CTR (US)
[not found] ` <CAKs0BQ7RyLZr+ZU=hAC4U7xXpE0+xvORTrvfzFYb6muA2TgM4Q@mail.gmail.com>
2012-11-18 17:18 ` Jörg Rosenkranz
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=CAMK1S_hCk3QdDn8XnXVisL1i2V0iPCZBYN989JmZ3JYr7ckRrA@mail.gmail.com \
--to=sitaramc@gmail.com \
--cc=andrew.ardill@gmail.com \
--cc=enrico.weigelt@vnc.biz \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=javierdo1@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).