CVS won't check in my .mcw file
 

I've set up TortoiseCVS. I'm using :local: mode, and mounting the repository as a drive on client machines, having checked the policy selection that allows repos on networked drives.

When I check in (commit) the project files, CVS says that "Norm" is not a valid editor of FrcCode.mcw (Norm is the user on the machine doing the checking in). If I uncheck that one file, all other files check in okay.

Any ideas?

FWIW, the repo is on a Win2K machine. The client in this case was an XP machine.

-Norm

Re: CVS won't check in my .mcw file
 

I haven't seen that particular error message before, but checking in the .mcw file isn't necessary. It defines things like window positions which isn't important to version control. If you are sharing the repository, everyone should have their own .mcw file.

Edit: found the following in the MPLAB users manual: It's likely that MPLAB has the files locked from editing and that is causing the error message.

Re: CVS won't check in my .mcw file
 

Thanks, that's a big help.

But isn't one of those files the equivalent of a Makefile? If I add new files to the project, but I can't commit the (Makefile), how will the next guy who does an update know that there are new files that go into the build? Won't he have to manually add the new files to the project? And how would he even know that there are new files that should be added?

Maybe I'll get a chance to answer these questions for myself this evening.

Re: CVS won't check in my .mcw file
 

You're thinking of the .mcp file.
That's the one that keeps track of which files are in your project.

Re: CVS won't check in my .mcw file
 

Any reason you're using CVS?

We got an SVN repo set up and it's been great - far more modern than CVS also.

Re: CVS won't check in my .mcw file
 

Why CVS? No great reason, really, except that I was able to convince a colleague from work to come out and set it up as well as the wireless network for the shop. He chose CVS. We're using TortoiseCVS as the interface, which allows us to use it with rightclicks in Explorer instead of a command line interface.

There's a lot of discussion in this forum about the pros and cons of SVN vs. CVS etc. I'm just happy to have something running.

And thanks to Mark Mc. for letting me know that the .mcp file plays the role of the Makefile.