Ok, I've committed those changes into the rel_2_4_3rc1 branch, and now all of the tests and make stuff is working (for me, at least), just like it is for the main branch. Please test away.
-Judd On Wed, 2006-08-09 at 10:29 +1200, Christian Soeller wrote: > If the goal is to fix up problems with the release candidate you need to > check out a working copy of the rel_2_4_3rc1 branch and edit and commit > on that one. Alternatively, you can switch your current working copy to > this branch. The online CVS book has examples on this. > > The release manager can always migrate patches from the main branch into > this one if they see fit. > > See also http://cvsbook.red-bean.com/cvsbook.html#Branches > > Hope this helps, > > Christian > > Judd Taylor wrote: > > Me neither. I think I committed to the main CVS branch. If someone out > > there wants me to do something different, just let me know. > > > > -Judd > > > > On Tue, 2006-08-08 at 13:25 -0400, Chris Marshall wrote: > > > >>Was this applied to the rel_2_4_3rc1 branch? > >> > >>I would like to keep fixes to get 2.4.3 out the > >>door in the release candidate branch. General, > >>non-specific fixes for the 2.4.3 release could go > >>in the main branch. > >> > >>However, I'm not familiar with the standard > >>method for release management and am willing > >>to be advised by the more experienced hands. > >> > >>--Chris > >> > >>Judd Taylor wrote: > >> > >>>I just committed fixes to the CVS for the HDF > >>>and Proj modules to address the issues brought > >>>to my attention in the last couple of days. > >>> > >>>Please retest if you were having problems, and > >>>let me know if any still exist. > > > > > > _______________________________________________ > > Perldl mailing list > > [email protected] > > http://mailman.jach.hawaii.edu/mailman/listinfo/perldl > > _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
