Harry Putnam writes: > > I don't do many imports... maybe 5-5 in the last 10 yrs.. > And never did one that was not the start of a new repository. > > Is it a misuse of import to use it to start a new directory hierarchy > beneath some exiting hierarchy in CVSROOT?
Not at all -- CVS really doesn't care about the directory structure. > On a remote machine (on home lan) I've imported a directory hierarchy > like so: > > cvs import -m "some blab" base/NEW_IMPORT blah start > > Now, back on the local host which is also the cvs server for the home > lan, I go to the checked out module, which hasn't been used since I > did the import. > > I run `cvs -n update -dP'.. just checking. > > It shows no output. Yes, that's normal. > Shouldn't cvs be telling me about the newly imported directory > hierarchy under `base', and be listing files needing to be updated? Yes it should, but the way the CVS code is structured prevents update with -n from doing everything that it does without the -n. Actually running the update (without the -n) will do the right thing. -- Larry Jones Oh, now YOU'RE going to start in on me TOO, huh? -- Calvin
