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.
On Fri, 3 Sep 2004 07:42:47 +0200, "Oliver Giesen" <ogware at gmx.net> wrote: >> >Again, you /could/ checkout or export by revision number. It's just not >> >terribly useful as some revisions typically change less often than >> >others. >> > >> Did you try this? >> I did and received an error message from cvs... > >To be honest, no. This was the one point I replied to for which I was not >speaking from actual experience. I just couldn't imagine why there should be >a special restriction as in all other cases tags, branches and revision >numbers could always be used interchangeably... >If you did try, I'll take your word for it for now. What did the error >message say? > In actual fact I tested the cvs export command rather than the checkout. Now I have done it both ways again and the result is as follows: C:\test\Exporttest>cvs export -r 1.1 CVSMailer cvs [export aborted]: tag `1.1' must be a symbolic tag C:\test\Exporttest>cvs checkout -r 1.1 CVSMailer cvs server: Updating CVSMailer U CVSMailer/BranchTest1.txt ... The checkout proceeds and gets all files to revision 1.3 (which is not terriby useful but apparently possible at least). I had problems with the export one before in my setup scripts because that is one place where it makes sense to get a particular revision out of CVS for the setup generation. My batch files do cvs export commands on all needed files and then builds the setup, but it failed when I added the revision info so I had to tag that file instead and use the tag in the export command. So cvs export and cvs checkout treat the -r flag differently.... I thought that the parsing was common and that it would work exactly the same, but I was proven wrong... /Bo (Bo Berglund, developer in Sweden)