Yet again, my original question has been ignored. > > Any chance that my fix for bug #2456 (see patch attached to > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2456) > will get into 1.5.2? > > > > Sean
This is the 3rd time I have asked for feedback on this and have received no response whatsoever. If the patch is flawed, fine, but it would be nice to get a response in either case. Am I missing something here? > -----Original Message----- > From: Tinny Ng [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 23, 2001 3:28 PM > To: [EMAIL PROTECTED] > Subject: Re: Xerces-C 1.5.2 status update ... > > > John, > > I think there are two ways: > > 1. A bugzilla bug is changed to FIXED resolution when its fix > is committed to > the CVS. Thus to get a list of all bugs fixed in the latest > code base since > last release, try specifying the following query field in > Bugzilla, e.g. > - Where the field(s) => select resolution > - dates => 2001-07-18 to Now > - changed to value => FIXED > where 2001-07-18 was the last release date. > > This will give you a list of all the bugs that got FIXED > state since 2001-07-18. > > 2. Grep the latest version of doc/release.xml from CVS, or check the > doc/html/release.html that is distributed in the latest > nightly build. This > file may not always have the latest status, but can still > give you some clue. > > Tinny > > [EMAIL PROTECTED] wrote: > > > Excuse the ignorance, but I've never managed to get a > listing of all things > > fixed between 1.5.1 and present day using bugzilla.... > especially usefull > > when I want to check what's been fixed since the last > official release. > > > > Can someone clue me up on this one? Thanks! > > > > John > > > > -----Original Message----- > > From: Bright, Sean [mailto:[EMAIL PROTECTED]] > > Sent: 23 October 2001 14:02 > > To: '[EMAIL PROTECTED]' > > Subject: RE: Xerces-C 1.5.2 status update ... > > > > Any chance that my fix for bug #2456 (see patch attached to > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2456) > will get into 1.5.2? > > > > Sean > > > > > -----Original Message----- > > > From: Tinny Ng [mailto:[EMAIL PROTECTED]] > > > Sent: Tuesday, October 23, 2001 8:46 AM > > > To: [EMAIL PROTECTED] > > > Subject: Xerces-C 1.5.2 status update ... > > > > > > > > > Hi, > > > > > > Just wanna to update you about the Xerces-C 1.5.2. It is ready. > > > However, PeiYong also told me his test against Mark Weaver's patch > > > (Bugzilla Bug 880, fix for Initialize/Terminate problem) is > > > also almost > > > done. So I would like to wait for him so that this > important patch is > > > also included in this release. May be a couple more > days, be patient > > > .... :-) > > > > > > Regards, > > > > > > Tinny Ng > > > XML Parsers Development > > > IBM Toronto Laboratory, email: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -------------------------------------------------------------- > ---------- > > For more information about Barclays Capital, please > > visit our web site at http://www.barcap.com. > > > > Internet communications are not secure and therefore the Barclays > > Group does not accept legal responsibility for the contents of this > > message. Although the Barclays Group operates anti-virus > programmes, > > it does not accept responsibility for any damage whatsoever that is > > caused by viruses being passed. Any views or opinions presented are > > solely those of the author and do not necessarily represent > those of the > > Barclays Group. Replies to this email may be monitored by > the Barclays > > Group for operational or business reasons. > > > > > -------------------------------------------------------------- > ---------- > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
