From: Asger Ottar Alstrup <asger@area9.dk>
To: git@vger.kernel.org
Cc: Avery Pennarun <apenwarr@gmail.com>,
Alexander Gavrilov <angavrilov@gmail.com>
Subject: git subtree as a solution to partial cloning?
Date: Mon, 25 May 2009 09:35:38 +0200 [thread overview]
Message-ID: <8873ae500905250035h74fc366ct907998c62e518fcf@mail.gmail.com> (raw)
I am considering different ways to get git to handle repositories with
very big files in a setup where partial clone is required, and it
seems git subtree might be a part of the solution.
Does git subtree support splitting at the file level, or only at
directory level? Also, how are conflicts handled when you subtree
merge changes back to the master? For this to work in practice, I
suppose the users of the split repositories should see the conflicts
and fix them themselves. Can the reduced split repositories reuse pack
files from the original repository? Can you think of any other
limitations to git subtree that would prevent it from working with big
files to support a partial cloning setup?
The alternative seems to be git sparse checkout extended with
non-existing narrow clone, but it seems that a git subtree based
approach might be simpler.
Regards,
Asger Ottar Alstrup
next reply other threads:[~2009-05-25 7:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 7:35 Asger Ottar Alstrup [this message]
[not found] <8873ae500905250021p20e7096dwf5bc71c36c4047b@mail.gmail.com>
2009-05-25 7:59 ` git subtree as a solution to partial cloning? Avery Pennarun
2009-05-25 9:33 ` Asger Ottar Alstrup
2009-05-25 15:50 ` Avery Pennarun
2009-05-25 17:35 ` Asger Ottar Alstrup
2009-05-25 17:54 ` Avery Pennarun
2009-05-25 18:28 ` Asger Ottar Alstrup
2009-05-25 19:18 ` Avery Pennarun
2009-05-25 23:26 ` Jakub Narebski
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=8873ae500905250035h74fc366ct907998c62e518fcf@mail.gmail.com \
--to=asger@area9.dk \
--cc=angavrilov@gmail.com \
--cc=apenwarr@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 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).