On Fri, Jan 25, 2002 at 06:08:44PM -0800, Sean 'Shaleh' Perry wrote: > ok, cvs is up to date on sf.net. It even has 0.62.1pre0 which is not released. > > The website shows (0 commits, 0 adds). Not sure how it tracks this. My usual > usage of cvs is: > > cvs import "blackbox version" blackbox blackbox blackbox-0_XX_X > > so at any time you can do > > cvs co -rblackbox-0_XX_X to look at a version. > > for some reason it does not consider my usage a commit or an add. > cvs is being used, just not in the way some people are accustomed > to seeing.
The way you do this normally is to commit commit commit, and when you make a release/prerelease, do a cvs tag, which will tag the revisions in your current working directory. When you code freeze for a release, make a branch. edit some files cvs commit cvs tag -bR releng_x_y commit some stuff for release cvs commit -r releng_x_y cvs tag -R release_x_y_pre1 fix bugs cvs commit -r releng_x_y cvs tag -R release_x_y_pre2 happy? build release tarballs. cvs tag -R release_x_y Vendor branches don't give you good commit history. -- David Terrell | "Consumerism is neat." [EMAIL PROTECTED] | - Brian Swetland http://wwn.nebcorp.com/ |
