cd top-of-your-imp-sim-tree cvs update
to update with someone else's branch, or an intermediate tag named, some-branch, you would type:
cd top-of-your-imp-sim-tree cvs update -j some-branch
gmake unimportfrom the top of your imp-sim tree.
Merging differences between 1.3 and 1.3.20.1 into files cvs update: Updating src/mmc cvs update: file mmc_main.c only in revision i6-wil-m7-1 cvs update: file mmc_init.c only in revision i6-wil-m7-1 cvs update: file mmc_debug.c only in revision i6-wil-m7-1 cvs update: file mmc_stat.c only in revision i6-wil-m7-1 cvs update: file mmc_inter.c only in revision i6-wil-m7-1 cvs update: file mmc_prefetch.c only in revision i6-wil-m7-1Curious as you are, you even check what the status of those files are in the named branch with
cvs stat src/mmc/mmc_main.cand you get back nothing.
In all likelihood, the person who made the tag failed to do the unimport before they tagged. Even though those files are not part of the repository, they can be found in the Attic (since they at one time were part of the repository). CVS, in it's wisdom, decides that the files should be part of the tree, somehow and sort of, but not entirely, and then yells at other people who try to update based on that tree. Of course, the person who performed the tag thinks everything is hunky dorey.
rm file cvs remove file cvs commit fileIt's as simple as that!
If the file is not removed properly, it will continue to reappear. Don't worry, just complain to the mergemaster and to the person who was responsible for removing the file originally.