From: Michael H. <mic...@ju...> - 2001-09-19 18:42:45
|
I've labeled and branched sdcc. The new branch is sdcc-230. The normal HEAD branch is open for checkins. Ah, so, what does this mean? * If you want to fix a bug in the 2.3.0 branch, you need to switch to it, make your changes and then check in. You will stay in that branch until you reset to the main branch. Try: cvs update -r sdcc-230 Make changes cvs ci To reset to the main development branch, use: cvs update -A To merge your changes back into the main branch from the 2.3.0 branch, use: cvs update -A (to get onto the main branch) cvs update -j sdcc-230 (to merge from sdcc-230) cvs commit (to commit the merges) * Normal development is unchanged. Hopefully the release candidate should be ready in a few hours. I'd like to recommend that the development versions have a odd patch number (2.3.1) and the release versions a even patch number (2.3.2) as this most easially fits into the way cvs does things. -- Michael On Wed, 19 Sep 2001, Michael Hope wrote: > I'm going to label and branch in about an hour. More news after that. > > -- Michael > > On Tue, 18 Sep 2001, Scott Dattalo wrote: > > > > > Is 2.3 eminent? Should I hold off on a boat load of commits (that > > theoretically affect only the PIC port)? > > > > Scott > > > > > > _______________________________________________ > > sdcc-devel mailing list > > sdc...@li... > > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > > > > > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > |