> I've noticed some strangeness with the release22-maint branch. I made > a documentation change there this morning, and CVS gave the change a > really weird version number when I checked it in. Looking further, it > looks like the previous checkin for that file (Doc/tut/tut.tex) has > some strangeness as well. The branching tags are also pretty > whacked. This is an excerpt of the "cvs log" for the file: > > ------------------------------------------------------------------------ > RCS file: /cvsroot/python/python/dist/src/Doc/tut/tut.tex,v > Working file: tut.tex > head: 1.158 > branch: > locks: strict > access list: > symbolic names: > r212: 1.133.2.5 > r212c1: 1.133.2.5 > release22-mac: 1.156.4.1 > release22-maint: 1.156.4.1.0.2 > release22: 1.156.4.1 > release22-branch: 1.156.0.4 > release22-fork: 1.156 > ------------------------------------------------------------------------ > > Note the revision number for release22-maint; it looks like it's a > branch created from a branch created from a tag on a branch(!). All > the while, I've been thinking that branches, once created, are > independent (identified by the third component of the revision number > for any given file). I still think they're supposed to be. I think you must've used a tag to bvase your branch, and that tag was already on a branch. --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4