Make Plugins into Submodules

[ProLoser]

You really shouldn't be tracking the files of all the plugins in the parent projects. They should be broken down into their own respective repositories so that they may keep their own histories intact. This will lighten the master repo and make updating easier. It may call for forking all the plugins yourself just so you can make modified builds of all of them

[rynop]

I'm a total github (and git) noob - let me try to rephrase to see if I get what your saying...

Today, I manually track the external github projects (like mcurry's asset for example) and any changes in the external project I have to manually copy into my github project.

You saying this is not a good way to do it (I totally agree, its a pain in the ass) and that instead of manually tracking, there is some way to "link" the other projects into my project in the master? So that if a change goes into mcurrys github asset plugin, it will propigate to my repo for free??

If that is correct, how do I do that? I know I probably need to just read up on forking etc but if you can give me some pointers / lead me in the right direction i'd really appreciate it (as I currently don't have much time to spend on cakeplate)

thanks in advance Dean
-Ryan

[rynop]

Cool thanks. Yea I saw your skel based project - I'll have to take a closer look. I like the app_controller::loadComponent() - OK if i use that in CakePlate?

On a side note, does CakePHP-Cacheable work well with memcached based cache? I'm gonna give it a try, but just curious how much real world use the plugin has had being backed by memcached.

[rynop]

closing all 1.3 issues