Hi all,
OK, the patch file as it exists is crashing the patch program with a failed
assertion.
Mark, can you make sure your patch is compatible with the latest CVS and
provide a CVS diff? Also, actual copies of the new source files instead of
diffs (XalanParsedURI.cpp and XalanParsedURI.hpp) would be much easier to
deal with.
Otherwise, I don't think I can get it in, because I'm too busy right now to
handle a manual patch.
Thanks!
Dave
David N
Bertoni/Cambridge To:
[email protected]
/IBM cc: (bcc: David N
Bertoni/Cambridge/IBM)
<david_n_bertoni@ Subject: Re: Upcoming Xalan-C++
1.5 release
us.ibm.com>
03/19/2003 01:29
PM
Hi Craeg,
I'll have to look at the extent of the patch, if I can apply it to the
latest source, and see what the impact is. Unfortunately, I've already
built some of the platforms, so this will delay things for at least a few
days.
Dave
Craeg K Strong
<[EMAIL PROTECTED] To:
[email protected]
rtners.com> cc: Mark Weaver
<[EMAIL PROTECTED]>, (bcc: David N
Bertoni/Cambridge/IBM)
03/19/2003 01:13 Subject: Re: Upcoming
Xalan-C++ 1.5 release
PM
Drat.. this bug is a show-stopper for us. Um. Would it be possible to
thaw 1.5 just a bit?
Regards,
--Craeg
Mark Weaver wrote:
>Whoops, looks like I've missed my opportunity to get the URI fixes in. In
>retrospect, I've finally gotten around to posting my patch for this:
>
>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16737
>
>which has both the patch and a test application. It's against the 1.4
>release, but will probably apply painlessly against 1.5 as the changes are
>very localised. (One for the 1.6 tree, hopefully).
>
>Mark
>
>
>
>>-----Original Message-----
>>From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROTECTED]
>>Sent: 18 March 2003 19:27
>>To: [email protected]
>>Subject: Upcoming Xalan-C++ 1.5 release
>>
>>
>>
>>Hi all,
>>
>>The CVS repository is frozen, and the sources have been tagged for the
1.5
>>release. We're now starting to do candidate release builds which we will
>>make available for testing purposes. Look for future announcements
>>regarding which platforms are ready and where you can obtain the
>>distribution.
>>
>>The last hurdle we have is updating the documentation, which will take at
>>least several days, and perhaps longer. This is a perfect opportunity to
>>mention that our documentation no longer has an official owner. So, if
>>there's someone out there who enjoys writing, now would be a good time to
>>volunteer!
>>
>>If all goes well, I hope we can post the final release early next week.
>>
>>Dave
>>
>>
