Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [stellation-res] Fix for 32077 posted

I've just applied validated the patch -- good job!
I will check the modified files into CVS shortly (there are quite a few).

Note: in preparing to validate the patch yesterday, I found that
both the current and revised (Bugzilla #33339) test scripts failed
with the current CVS source image, at the beginning of test 6,
with a timestamp-related error message.

Since the revised script worked the day before, on source lacking
the 32077 fixes, I am somewhat baffled.  Just to be clear, my
successful test run today used:
* Current CVS Java source, with 32077 applied
* Revised test script (CVS ant script + 33339)
* Revised build script (CVS build-core.xml script + 31589)

Since I authored patches for 33339 and 31589, I can't verify them myself.
Could someone please verify them so we can have a buildable, testable
image in CVS?  Please?

Thanks,
Jim

At 02:47 PM 2/20/2003, Mark C. Chu-Carroll wrote:

There's a patch fix for 32077 posted in bugzilla. I'd appreciate it if
someone could give it a check. (Any non-committers out there who'd
like to start getting involved? The active commit team is quite small
at this point, and we could use some help! Feel free to do the audit
checks on incoming changes!)

        -Mark


--
Mark Craig Chu-Carroll,  IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
***             http://www.eclipse.org/stellation
*** Work: mcc@xxxxxxxxxxxxxx/Home: markcc@xxxxxxxxxxx


_______________________________________________
stellation-res mailing list
stellation-res@xxxxxxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/stellation-res


--------------------------------------------------------------------
Jim Wright, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: jwright@xxxxxxxxxxxxxx ------- Personal Email: jim.wright@xxxxxxx



Back to the top