Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [wtp-dev] Source updates?

Ed, thanks for the offer to merge, but, to avoid duplicated work, thought I would mention we will be doing a little work to assess what, exactly, the modifications were, and what, if any is the best way to merge back in to soon-to-be active stream (as we make it public, that is, sorry for the offset delay).

The zipped up contribution appears to contain everything (from servers to webservices) but from what I've read on newsgroup, editing was the function most talked about, so I'd expect fixes/improvements to be in that area. So, someone from our editing team will do some diffs on whole thing and make an initial inspection to determine nature and extent of changes.  We'll decide second step from there.

I'm sure in future Genuitec would be happy to contribute fixes in the form of patches against CVS version, once that version is in CVS! (and we've be happy to have them :)

And, I should add, if you've already done any assessment yourself or have an idea of what was fixed, exactly, don't hesitate to make your own recommendations to this list.

Thanks again,


"Ed Burnette" <Ed.Burnette@xxxxxxx>
Sent by: wtp-dev-admin@xxxxxxxxxxx

10/11/2004 03:40 PM

Please respond to

RE: [wtp-dev] Source updates?

Ok. When you say "the code will be checked into CVS" do you mean checked in at under the webtools repository or do you mean something else?
Also, is there a plan for merging in the Genuitec fixes or is that still to be decided?
I could help with merges but I don't want to duplicate somebody else's work.

From: wtp-dev-admin@xxxxxxxxxxx [mailto:wtp-dev-admin@xxxxxxxxxxx] On Behalf Of Arthur Ryman
Monday, October 11, 2004 1:35 PM

 IBM is completing a product release and will refresh its contribution in a few weeks. The refresh will include bugs fixes, completed function, etc. At that time, the code will be checked into CVS and we will work on it there. We have held off working in CVS since we cannot afford to maintain dual code streams.

Back to the top