I'm OK with the idea - nothing implicit about that :-)
Not that I'm happy to whip this dead horse again, but one thing
that's kind of annoying is that a lot of this is working around
subversion. Subversion doesn't do branch updating well, so the
option to "create a branch for experimental tools that require core
changes" involves a lot more maintenance work than with a properly
distributed revision control system. Changesets have to be manually
merged and something outside the system needs to remember what was
merged so consistency can be maintained.
Here's a thought: if we're stuck with subversion, how about
maintaining core changes (and the experimental tools, too) as patches
managed by a patch management system like quilt?
http://savannah.nongnu.org/projects/quilt
Regards,
Robert.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Valgrind-developers mailing list
Valgrind-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
