Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Tony, Can you provide a receipt for those who need commit -r to add new files directly into a branch? Example: cvs commit -m Test -r my_branch foo.txt ***** CVS exited normally with code 1 ***** commit: invalid option -- r Usage: cvs.exe commit [DnRlf] [-B bug | -b bug ] [-m msg | -F logfile] [-r rev] files... -b bugid Only commit files related to bug. -B bugid Mark files with bug. -c Check for valid edits before committing. -D Assume all files are modified. -F logfile Read the log message from file. -e Keep edited files. -f Force the file to be committed; disables recursion. -n Do not run the module program (if any). -l Local directory only (not recursive). -m message Log message. -R Process directories recursively. (Specify the --help global option for a list of other help options) Thanks in advance Daniel Tony Hoyle wrote: > Bo Berglund wrote: > >> Unless Tony has removed the -r option in 2.5 it is still there, >> however you cannot commit to 2.0 anyway because that is not a valid >> revision number. All numbers ending with .0 are reserved for other >> purposes... >> Try with 2.1 instead. > > > It's gone compeletely. > > Too many people trying to use it instead of tags.. I changed it a > little while back. In a future revision (2.5.03/04) the whole number > scheme is likely change completely as I start to link in the database > parts - this will mean that anything that is set will get overwritten > anyway. > > Tony