From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Thomas Adam <thomas.adam22@gmail.com>
Cc: Chani <chanika@gmail.com>, git@vger.kernel.org
Subject: Re: partial checkouts
Date: Mon, 25 May 2009 11:51:46 +1000 [thread overview]
Message-ID: <fcaeb9bf0905241851i768b4c5bl9bca9faeb12ff4a@mail.gmail.com> (raw)
In-Reply-To: <18071eea0905240857x2433e7a1x5776def3209afbf5@mail.gmail.com>
On Mon, May 25, 2009 at 1:57 AM, Thomas Adam <thomas.adam22@gmail.com> wrote:
> 2009/5/24 Nguyen Thai Ngoc Duy <pclouds@gmail.com>:
>> On Sun, May 24, 2009 at 7:00 AM, Chani <chanika@gmail.com> wrote:
>>> checking out the entire git repo isn't really feasible, because once KDE
>>> finishes switching to git that'll mean checking out all of KDE.
>>> I don't think that turning every doc folder into a submodule is feasible,
>>> either - they sound kinda awkward to work with, and I can imagine lots of
>>> people getting confused and messing them up...
>>
>> If you don't mind cloning the entire git repo (which may be quite
>> large in KDE case, I guess), then you may want to try "sparse
>> checkout". The patch series is available as a topic branch "tp/sco" in
>> this branch:
>>
>> http://repo.or.cz/w/git/pclouds.git?a=shortlog;h=refs/heads/inst
>>
>> Or I can send the patch series to you. It lets you specify what part
>> of the tree you want to checkout.
>
> I recall following this series when you first announced it. Do you
> have any plans to try and get it included in mainline? ISTR there was
> some more work needed to be done on it before then.
It was pulled off because of big, intrusive and not well-designed patches.
http://mid.gmane.org/20081128192033.GF23984@spearce.org
I may submit it again when I get code insertions down to ~500 lines or
something like that ;-) Anyway you could always help by giving more
use cases to test against the current design.
--
Duy
prev parent reply other threads:[~2009-05-25 1:53 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
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 [this message]
[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=fcaeb9bf0905241851i768b4c5bl9bca9faeb12ff4a@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=chanika@gmail.com \
--cc=git@vger.kernel.org \
--cc=thomas.adam22@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).