Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a personal bitkeeper repository and would like the version numbers to change from 1.xxx to 2.xxx.
My usage is a perl library and I have made major changes to the calling sequence and would like the SCCS strings that automatically get updated to reflect the new sequence. This way the use Module VERSION method will easily determine which calling sequence without having to specify 1.32 is the old one and 1.33 is the new one, for example.
BitKeeper doesn’t support changing the major number (or release number in SCCS lingo). Also note that coding logic that depends on revision numbers is fraught with peril as they can be unstable (e.g. what is revision 1.33 on your tree might be moved to revision 1.28.1.1 once you push).