Ok. I've submitted a file to CVS and it seems to have worked in as far as there were no errors and there's a record in the resource history for it now and when I "compare with 2.1 release branch" there's no differences. But I'm not sure whether there's supposed to be a tag in the resource history for the version I've submitted? The change has been created as version 1.7.6.1 on the 2.1 release branch (I would assume) as that is the CVS branch I'm configured to. But I'm not sure whether I am supposed to add a SLIDE_2_1_RELEASE_BRANCH tag to the file or whether there are just no tags currently associated with it right now. Or that it inherits the tag from its parent version 1.7 which does have a SLIDE_2_1_RELEASE_BRANCH tag.
Let me know whether the commit worked as expected. Also, how do I submit to the HEAD? I assume that I will need a second copy the slide tree to work with synchronized with the HEAD? Thanks, Warwick > -----Original Message----- > From: Warwick Burrows [mailto:[EMAIL PROTECTED] > Sent: Monday, December 06, 2004 4:13 PM > To: 'Slide Developers Mailing List' > Subject: Suggested bug fixes for 2.1 release branch commit > > > Hi guys, > > I would like to test my commit status by committing a couple > of fixes to CVS that I have recently submitted as patches to > bugzilla. They are defects 32460 and 32483. Let me know if > you have any issues or questions about the fixes, or warnings > or suggestions about committing. Should I also commit the > changes to the CVS HEAD as well? > > Finally, I've read the Apache committer's guidelines, but are > there committer's guideliness for Slide that I should also read? > > Thanks, > Warwick > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
