I find undocumented behavior for cvs commit -r option.
(I suppose these are documentation bugs.)
In cvs.info,
>commit options
>
>`-r REVISION'
> Commit to REVISION. REVISION must be either a branch, or a
> revision on the main trunk that is higher than any existing
> revision number (*note Assigning revisions::). You cannot commit
> to a specific revision on a branch.
>
> `commit' also supports these options:
I try this option with cvs-1.10.8.1, and over :local: method.
On trunk, when working revision is X.Y, cvs allows:
X
X.
X.Y+n
X.Y+n.
X.Y.Z
X.Y.Z.
(X, Y, Z and n is number.)
3-number format makes new branch.
On branch (A.B.C), when working revision is A.B.C.D, cvs allows:
A.B.C
A.B.C.
A.B.C.D+m
A.B.C.D+m.
A.B.C.D.E
A.B.C.D.E.
(A, B, C, D, E and m is number.)
5-number format makes a new branch.
After I checkout BRANCH-1,
I execute `cvs commit -r BRANCH-2 FILE', then I get:
cvs commit: Up-to-date check failed for `FILE'
cvs [commit aborted]: correct above errors first!
I cannot understand the description in info.
And then, cvs commit -r option makes a working file stickied.
--
KOIE Hidetaka <[EMAIL PROTECTED]>
