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.
Hello again, Bo!
> Try with 2.1 instead.
Ok, you're right. I tried to commit with "-r 2.1" (as you said) or any else
"revision", and the cvs message is the same: "invaid option -- r".
the "work.txt" head revision is 1.5, so 2.1 would be a good revision.
there is a branch in the history of this file named "elagazas", but the "-r
elagazas" option is "invalid option", too. I try either an existing branch,
or a revision number (higher than any existing rev. num.) produce an
"invalid option -- r" message.
> But then again, whay are you dealing with the revision numbers in the
first place?
> They are to be considered as private information for the CVS server in
order
> to keep track of changes and they serve no outside use at all.
Yes i know, just tried it! This option is in the documentation... I think I
try it again. :-))
.. and some month ago (last november) still worked.
Sometimes I do cvs training course for the developers of our company, and i
don't want to say stupidity.
some option work, some not... some option worked last year, and now not...
This works for you, Bo?
Zoltán
---- Bo Berglund wrote: ----------------
>From the CVSNT helpfile on the commit options:
<quote>
-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
(the section called ?Assigning revisions?). You cannot commit to a
specific revision on a branch.
</quote>
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.
But then again, whay are you dealing with the revision numbers in the first
place?
They are to be considered as private information for the CVS server in
order
to keep track of changes and they serve no outside use at all.
/Bo
-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of
Zoltan.Szathmary at generali.hu
Sent: den 26 april 2005 13:01
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: [cvsnt] commit with -r option [ Vírusmentes]
Was this good old option: -r revison deleted from commit options?
command: cvs commit -m "msg" -r 2.0 -- work.txt
cvs message is: 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.
Zoltán