uberlinuxguy committed revision 8 to the Parsec SVN repository, changing 22 files.
2012-05-09 18:07:50 PDT in Parsec
uberlinuxguy added sulucnumoh to the Parsec project.
2012-02-25 10:53:14 PST in Parsec
uberlinuxguy changed the public information on the Parsec project.
2012-02-11 08:39:32 PST in Parsec
uberlinuxguy changed the public information on the Parsec project.
2012-02-11 08:27:09 PST in Parsec
uberlinuxguy changed the public information on the Parsec project.
2012-02-10 13:18:38 PST in Parsec
uberlinuxguy changed the public information on the Parsec project.
2012-02-10 13:18:37 PST in Parsec
uberlinuxguy changed the public information on the Parsec project.
2012-02-10 13:18:37 PST in Parsec
uberlinuxguy added crazy-spence to the Parsec project.
2012-02-10 10:27:28 PST in Parsec
The system may have an internal way to track memory, since almost all mallocs/frees are done through the ALLOCMEM()/FREEMEM() macros. But it would be a good idea for someone to get a memory profile and look for bugs and breaks in the trunk/ code. I want to make sure that's 100% stable and free of leaks.
2012-02-10 05:30:56 PST in Parsec
uberlinuxguy committed revision 1 to the Parsec SVN repository, changing 2802 files.
2012-02-09 16:12:00 PST in Parsec