Daniel Bron writes: > > My cvs client, wincvs, supports browsing the modules on the server. > However, whenever I try to do this, I get an error to the effect that the > 'modules' file doesn't list any modules. My question is, am I responsible > for populating this file?
Yes, should you want to do so. > Shouldn't the CVS server knwo what modules are in > a particular directory? Module names have nothing whatsoever to do with directory names. CVS is perfectly happy to take a relative path within the repository in lieu of a module name, so you don't have to define any modules at all. However, there is a command to list all the modules (co -c) but there isn't a command to list directories. > I'm reading the documentation on the 'modules' file, and it doesn't make any > sense to me. It says I'm supposed to supply a module name and a directory; > but all my modules are just subdirectories of my repository. Do I really > need to update this file every time someone adds or deletes a module? Yes, if you want "co -c" and things that depend on it to work. -Larry Jones Hello, local Navy recruitment office? Yes, this is an emergency... -- Calvin _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
