From: Johan Herland <johan@herland.net>
To: Chani <chanika@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: partial checkouts
Date: Sun, 24 May 2009 01:34:53 +0200 [thread overview]
Message-ID: <200905240134.53387.johan@herland.net> (raw)
In-Reply-To: <200905231401.11651.chanika@gmail.com>
On Saturday 23 May 2009, Chani wrote:
> [...]
>
> right now all I've thought of is one ugly hack: have a server that checks
> out all the kde git repos, pulls daily, copies all the doc/ folders into
> a documentation folder, and offers that folder up on the interwebs so
> that update_xml can rsync from it or download a tgz of it or something.
> there appear to be lots of images in the documentation, so it's not a
> small download - 200mb and growing. it still hasn't finished downloading
> all the externals...
Do you need the doc/ folders from _all_ kde git repos, or just from those
repos that you have currently checked out? In the latter case, you could
solve this by adding symlinks to all the doc/ folders inside the
documentation/ folder, and then make sure the software that traverse the
documentation/ folder recognize and skips symlinks. Of course, this won't
work if the translations project need _all_ doc/ folders accessible, but not
all the kde git repos.
> I'm kinda wondering if there'd be a way to use git-filter-branch to make
> a repo that only tracks the doc/ folder for a module - but I've no idea
> whether it'd have to be recreated from scratch every time someone changes
> something in the real repo's doc/
>
> can anyone think of a less ugly solution?
> what are the chances of git supporting this kind of partial checkout
> someday?
Check out git-subtree. It can split out a subdirectory into its own repo,
and re-integrate it back into the "parent" repo at a later date. git-subtree
has been posted as a patch to this list a couple of times without much
response, but it looks like an interesting alternative to submodules:
http://alumnit.ca/~apenwarr/log/?m=200904#30
If a lot of people find git-subtree useful, who knows, it might be included
in a future git version.
Have fun! :)
...Johan
--
Johan Herland, <johan@herland.net>
www.herland.net
next prev parent reply other threads:[~2009-05-23 23:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 21:00 partial checkouts Chani
2009-05-23 23:34 ` Johan Herland [this message]
2009-05-24 0:26 ` Chani
2009-05-24 19:45 ` Avery Pennarun
2009-05-25 3:07 ` Chani
2009-05-25 14:51 ` Aidan Van Dyk
2009-05-24 2:07 ` Nguyen Thai Ngoc Duy
2009-05-24 15:57 ` Thomas Adam
2009-05-25 1:51 ` Nguyen Thai Ngoc Duy
[not found] <1D6034426110564DA0DEA9EE9793B38357BE874673@NBE-MBX01.americas.swk.pri>
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=200905240134.53387.johan@herland.net \
--to=johan@herland.net \
--cc=chanika@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 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.