Jeff Decker writes: > > It looks like all the files you put into .cvsignore are to prevent > adding to the repository.
No. The sole purpose of .cvsignore and related features is to prevent CVS from constantly reminding you that certain files in your working directory are not under its control. > My question is I am getting the project from > a repository that already has files in it but once I get the file I want > cvs to ignore any future changes I make to the file. CVS has no facility for doing that. > I've found a horrible, bad hack to do this. If I go into the hidden cvs > folder and remove the file from the entries file, cvs will lose its > "link" to that file. This will work for commiting but if I do an update > on the project folder I belive it will try to either overwrite my > changes or ask me to merge manually (which is an annoyance). Actually, it will just tell you that your current file is "in the way" and ask you to move it. -Larry Jones Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us. -- Calvin _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
