Fabian Cenedese writes: > > We tag our sources from time to time as it should be. But for some > reason not all tags go into the val-tags file. In some repositories it's > even empty. According to docu this shouldn't matter as cvs will refill it > next time a tag is used.
CVS doesn't add tags to the val-tags file when they're created, only when they're referenced. Many times tags are applied "just in case" and never actually get used -- not recording them until they're used keeps the val-tags file lean and mean. > Problem is now that I get a "no such tag" error on some operations > if it is not in the val-tags file. And I don't know what to do to get it in. > Some operations work (log file, checkout module), some do not > (diff, checkout file). But those that work don't update the val-tags > file. If I manually add the tag in the val-tags file in the repo then also > the other commands work (with exactly the same settings as before). > But a different user had the same problems and adding the tag didn't > help in his case (assuming he did it right). He didn't. To determine if a tag is valid, CVS first checks the val-tags file. If the tag does not appear there, the specified files (NOT the entire repository) are scanned for the tag. If it appears in any of them, it is valid and is added to the val-tags file (unless you've specified the global -n flag). If you're getting "no such tag", then the tag really doesn't exist in any of the file you specified for the command (although it may exists in other files that you haven't specified). Commands like "log" don't require a valid tag -- you get generic log information in any case -- but you *do* get a warning that you perhaps overlooked. -Larry Jones I suppose if I had two X chromosomes, I'd feel hostile too. -- Calvin _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
