[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Branches and versioning.
From: |
cchgroupmail |
Subject: |
Branches and versioning. |
Date: |
18 Oct 2005 07:06:46 -0700 |
User-agent: |
G2/0.2 |
I know cvs recommends to ignore the versions of files and use tags, but
why is this so hard? Here's an example that creates a new repository,
adds a file o the trunk. Creates 2 branches 1.1.2 and 1.1.4. I update
to 1.1.4 and add a file. Why can't the version start with 1.1.4.1
instead of 1.1.2.1?
$ mkdir test
$ cd test
$ cvs import test test test1
$ cd ..
$ rm -fr test
$ cvs checkout test
$ cd test
$ touch file
$ cvs add file
$ cvs commit file
$ cvs tag -b test-1-1-2
$ cvs tag -b test-1-1-4
$ cvs update -r test-1-1-4
$ touch file2
$ cvs add file2
$ cvs commit file2
$ cvs status
===================================================================
File: file Status: Up-to-date
Working revision: 1.1
Repository revision: 1.1 /cvs/test/file,v
Sticky Tag: test-1-1-4 (branch: 1.1.4)
Sticky Date: (none)
Sticky Options: (none)
===================================================================
File: file2 Status: Up-to-date
Working revision: 1.1.2.1
Repository revision: 1.1.2.1 /cvs/test/Attic/file2,v
Sticky Tag: test-1-1-4 (branch: 1.1.2)
Sticky Date: (none)
Sticky Options: (none)
- Branches and versioning.,
cchgroupmail <=