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 email@example.com.
What 'cvs admin' options you use? When I run 'cvs -H admin' for my CVSNT binary, I get following output: > Usage: cvs admin [options] files... > -l[rev] Lock revision (latest revision on branch, > latest revision on trunk if omitted). (DEPRECIATED) > -m rev:msg Replace revision's log message. > -o range Physically delete (outdate) specified range of revisions: > rev1:rev2 Between rev1 and rev2, including rev1 and rev2. > rev1::rev2 Between rev1 and rev2, excluding rev1 and rev2. > rev: rev and following revisions on the same branch. > rev:: After rev on the same branch. > :rev rev and previous revisions on the same branch. > ::rev Before rev on the same branch. > rev Just rev. > -p [rev:]prop=val Set global or versioned property. > -q Run quietly. > -t[file] Get descriptive text from file (stdin if omitted). > -t-string Set descriptive text. > -u[rev] Unlock the revision (latest revision on branch, > latest revision on trunk if omitted). > (Specify the --help global option for a list of other help options) > > > THIS COMMAND IS FOR CVS ADMINISTRATORS ONLY. DON'T USE IT UNLESS YOU > KNOW EXACTLY WHAT YOU ARE DOING, AND WHAT THE CONSEQUENCES ARE. -- Best regards, Thomas Singer Oliver Koltermann schrieb: > Hello Thomas, > > Thomas Singer <cvsnt at smartcvs.com> writes: > >> No, it's 1 - without any period. Tony, what do you think? >>>> branches. But somehow the client managed to create a branch "1" on >>>> top of the main trunk revisions, which sounded a little bit strange >>>> to me. > > We use a (I guess not very common) scheme where "1"-Branches are used > to express file-to-project connections. The files belonging to one > project are marked with an alternate name for the main line (branch > 1). We do this for years now - I'm not sure if it could be done using > alias branches today. > > I have to call the "cvs admin" command to create this special branch > tags... so if this is the case at your clients site somebody (with > admin rights) there should know about this. > > Best regards, > O. Koltermann