The plan sounds fine to me. I expect it will be a straightformard
matter to merge the 2.5.0 release into my codebase. I'll write you
when it's done. I surmise that you would find it more convenient
to diff my repository yourself (assuming you are familiar with cvs);
all the information for doing so will soon be posted. Which do you
You are all correct that PCP should be more prominantly listed in
the project description, to shine more brightly on the radar. Do
understand that my project is suite of several tools, which PCP
is one important member of.
On Tue, 29 Nov 2005, Mark Goodwin wrote:
On Mon, 28 Nov 2005, Michael Werner wrote:
Are you feeding these changes back to Mark? I'd hate for the core PCP
code to become forked.
All my source code mods will be available from sourceforge, along with
the bug reports and release notes. It will be a simple matter for
Mark to diff the revision tags and get the mods. I've been careful to
ensure that my changes are compatible with SGI's internal build reqs.
Firstly, thanks for creating the new sf project. I agree with comments
from others that it needs a more accurate title & keywords, but in
concept it's an excellent step forward for PCP.
Your changes are against pcp-2.4.0 (as currently on oss.sgi.com), right?
The new release coming is pcp-2.5.0 so you'll need to reconcile against
the new code base. That shouldn't be a big deal but I'd rather you did
it and fed the resulting patches back to me. I'll push 2.5.0 up to
oss.sgi.com as soon as I can. I was hoping to include some libpcp changes
(as mentioned in earlier mail), but given the level of interest at the
moment, it may be better just to push 2.5.0 up to oss asap, and then have
a series of incremental minor releases as people feed patches back to me.
Does this sound like a good plan for all?