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 firstname.lastname@example.org.
Iakov Glubokiy wrote: > sounds reasonable... It really looks like this file is being rebuilt > when I want to get project by tag. > What this file for and what may alter/corrupt it? It lists the valid tags for the repository. Any tag in that file is assumed to exist in at least one file of the repository, so the tag validation returns very quickly. If you specify a tag that's not in there different commands will do different things... some will reject it immediately, and others will try to scan the repository for the tag to add it to val-tags. Normally this file is up to date so isn't a problem. Interestingly rtag updates this file and tag doesn't... not sure why (probably needs fixing). This means that the first update after a tag may take a couple of seconds to find it (although this isn't normally much of an issue especially if you tagged the entire repository). > We have commit script, which sends email notifications and tag script, > which restricts tag operations and send email notifications. > We also have traditional cvs for tests, but it listens nonstandart port > and nobody works with it for long time. The commit script shouldn't change anything, as val-tags is updated internally. Tony