As I said in my email, committing it is annoying because there's lots of weird SVN issues. I'll get around to this when I have some time to devote to taming SVN.
For now, if you'd like to help out or help me commit the code in the first place, I've uploaded a tarball of the code I'm working with here: http://baxter.cernio.com/sycamore_base.tar.gz --philip On 5/21/07, Adam Dewitz <[EMAIL PROTECTED]> wrote: > Philip, > > As you know there has been interest in hacking for some time now and > a lot of us having been waiting on you to commit your wikis code as > discussed during the development IRC meeting back in February. At > that time you thought this would be done by the end of March. > > I can appreciate that you were the sole architect of this project for > most its life, but by not committing your code, you block others from > helping you develop new features or squash bugs. We want to help you. > > I think the sooner you can commit these changes the better. We can > work together on merging them into trunk later. > > AD > > > > On May 18, 2007, at 5:26 PM, Philip Neustrom wrote: > > I know this is annoying for you guys. Checking it in is the hard > part, actually, as there's a bunch of non-versioned files, likely > crazy SVN breakage and manual merging (even for the branch itself), > and so forth. It'll take me a good day to do the commit, but I'll try > to get to it soon, especially now that there's interest in hacking > --philip > > _______________________________________________ > Sycamore-Dev mailing list > [EMAIL PROTECTED] > http://www.projectsycamore.org/ > https://tools.cernio.com/mailman/listinfo/sycamore-dev > _______________________________________________ Sycamore-Dev mailing list [EMAIL PROTECTED] http://www.projectsycamore.org/ https://tools.cernio.com/mailman/listinfo/sycamore-dev
