While working on merging 2.5 into our local trunk, I was doing a bunch of `svn merge –dry-run, svn merge` statements, and thought “wouldn’t it be nice if subversion could color-code the status output for me.” `svn help` didn’t produce a –color or –colorize option, so some [googling](http://www.google.com/search?q=colorize+svn+output&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a) lead first to a handy `sed` recipe: ...
So I finished merging in the Samigo 2.4 changes to the Rutgers code base yesterday the [instructions in the wiki](http://bugs.sakaiproject.org/confluence/display/SAM/Running+Samigo+2.4+in+Sakai+2.3) were actually very good — one small mis-merge on my part, but aside from the self-imposed pain the merge went quite smoothly. So far, the defaulting to off of the rich text areas is a ...
Soo… yesterday I completed my 2.3.1 Sakai vendor branch merge, and it’s now up on a Rutgers test server. It’s been sanity tested, and is ready for further banging. Speaking of banging… it did take quite a few steps to get to this stage… **Note:** 2.3.1 is a *small* merge, I think it was only ...
So… working on doing a relatively small SVN vendor branch upgrade, and so far finding things much more difficult than it seems like they should be. Problem 1: This was my fault — I checked in a vendor drop using `svn_load_dirs.pl` which had different line endings from my existing SVN tree. Of course, that resulted ...
[Single Mind Consulting – Summary of Sakai](href=”http://www.singlemindconsulting.com/files/white_sakai_described_v1.pdf) > Furthermore, Sakai is designed as a series of independent tools built upon a robust, standards-based framework (uPortal). > `` > Sakai’s uPortal is a powerful portal environment that utilizes the portlet specification to ensure interoperability. This particular perception – that Sakai contains an embedded uPortal instance which ...
