<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Josh,<div><br></div><div>so now we have a feature in trunk called "future". I don't know if I want it in my version of Cuis or not. I am not even sure what this feature consists of, in that I cant see what its boundaries are. However if I do I will want it to be a load-able extra, because some package I want to load may need it.</div><div><br></div><div>As a simpler example, take Mutex. Cuis doesnt have it, Magma uses it. It is a relatively isolated piece of functionality, it doesn't need to be managed inside the image, it can easily be a load-able feature.</div><div><br></div><div>Can you answer if you will, how you have packaged up this "future" innovation so that it would be useful to me?</div><div><br></div><div>If your answer is that you committed it to trunk, and I am expected to harvest it from trunk, I think you can forget it.</div><div><br></div><div>If your answer is that it is in Monticello inbox, then how can I get the most current version, surely the inbox version will have been tweaked in the image. And cuis being a kernel image doesn't have monticello.</div><div><br></div><div>Previously you said: "<span class="Apple-style-span" style="font-family: arial, sans-serif; -webkit-border-horizontal-spacing: 10px; -webkit-border-vertical-spacing: 10px; ">if we can achieve some of your goals without sacrificing the benefits of the new process"</span></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="-webkit-border-horizontal-spacing: 10px; -webkit-border-vertical-spacing: 10px;"><br></span></font></div><div>Hopefully this will help you to see that trunk is not really process offering any benefits at all. As far as I can see it is simply promoting sloppy work practices, where everything new you can think of gets thrown into the soup of a monolithic image, and now everyone can join in throwing stuff at the future (if you excuse the pun) image.</div><div><br></div><div>When I use the "grow" process I am now running and developing the same code, (even kernel level code that would break trunk) in all forks simultaneously. Every innovation or which is managed as a loadable extra, becomes a potential point of commonality between existing forks. The fact that trunk is not managing its features outside of the image, is a disaster. Heck you haven't even split System up (yet).</div><div><br></div><div>regards</div><div><br></div><div>Keith</div><div><br></div><div>===</div><div>"Branching is the new Forking"</div></body></html>