"Mark D. Baushke" writes:
Given the command 'cvs commit -r<value> filename'
... cvs allows you to play with dangerious
toys, so <value> may be a string comprised of
digits and dots. Doing this is NOT recommended...
Well, the cederqvist (Sec 4.3) actually uses this non-recommended use as an
example of how to use it.
- if <value> is a numeric form, then it may be a
revision number for a revision that does not
yet exist on its current branch.
For example, if the checked out filename is
revision 1.12 (and also happens to be the HEAD
of the main trunk), then <value> could be 1.13
or greater. In general, if you are on a
branch, you may specify the numeric branch
prefix of your branch and vary the final
number with a value that is not presently
represented in the delta information for the
filename.
You seem to suggest that <value> can be a revision number on a branch, such
as 1.2.2.1. Well, as mentioned in my previous post, this doesn't work in
the sense that this new revision will appear on the trunk, not the branch
1.2.2.
_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement
_______________________________________________
Info-cvs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/info-cvs
