From: Asger Ottar Alstrup <asger@area9.dk>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: git@vger.kernel.org, Alexander Gavrilov <angavrilov@gmail.com>
Subject: Re: git subtree as a solution to partial cloning?
Date: Mon, 25 May 2009 11:33:57 +0200 [thread overview]
Message-ID: <8873ae500905250233t52dce5b5v8ca88b9921a88437@mail.gmail.com> (raw)
In-Reply-To: <32541b130905250059n7b31cc1bk688e5f4bfaf83142@mail.gmail.com>
On Mon, May 25, 2009 at 9:59 AM, Avery Pennarun <apenwarr@gmail.com> wrote:
> On Mon, May 25, 2009 at 3:21 AM, Asger Ottar Alstrup <asger@area9.dk> wrote:
>> Does git subtree support splitting at the file level, or only at directory
>> level?
>
> Currently only at the directory level. In theory, there's nothing
> stopping us from working with any subset of files... but it's really
> much simpler this way (both to code and to explain) so I'd much rather
> leave it as is. Can you reorganize your tree so that you divide the
> needed files into different subdirectories?
No, that is unfortunately not so easy. If we could, I suppose we could
use submodules instead.
Are the subtree split and merge operations effective? I.e. how do they
scale with the size of the original and reduced repositories? I.e. is
it feasible to use hooks to automate the splitting and merging
whenever there are changes in the original or reduced repositories?
Regards,
Asger
next prev parent reply other threads:[~2009-05-25 9:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
2009-05-25 7:35 Asger Ottar Alstrup
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=8873ae500905250233t52dce5b5v8ca88b9921a88437@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).