This makes no sense.. CVS does this automatically and internally. when your developers commit or merge, it handles this stuff internally
On Thursday, March 21, 2002, at 12:35 PM, Alain Ravet wrote: > > Thomas Singer wrote: >> Please take a look at http://www.cvshome.org/docs/manual/ . >> .. .. for your understanding of how cvs works. > > > OK: I'll reformat my question (btw, this is an old request). > My mistake, I thought the hidden request was obvious, (and I posted in > the wrong list). > > > ********* > Request : > ********* > In the CVS dialog, next to the [Revision number]field, > Please add a smart (see below) "Increment revision number" button. > > It would be smart (not simply adding 1), by first finding in the CVS > repository the highest revision number, and adding 1 to it. > A little like using MAX (id) +1) to generate an new primary key. > > > > Alain Ravet > > > > > > > > Alain Ravet wrote: >> The problem >> - In project A, I commit files 10-20 times a day. >> Each time, I use a new number (1.31, 1.32, ..), by adding 1 to the >> latest >> number I used. >> - My colleagues work on the same project, and do the same. (1.31, >> 1.32,..) >> >> >> Question : >> How can I ensure the revision number for my next commit will be the new >> maximum, for the current project, across all developpers. >> Or, how to obtain >> Revision number = Max >> (all_files_in_the_project_repository.getRevisionNumber() ) > > _______________________________________________ > Eap-features mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-features > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
