Personal CVS repository?

[J Krugman]

My company has decided to collaborate with an academic group on an
on-going open-source project.  I'll be the only programmer on this
project; moreover, my contribution will probably be pretty
self-contained (i.e. I don't expect that anyone but me will be
modifying the code that I write for this.)

For reasons that I'm not too clear on, my supervisor has instructed
me that he must review my code before each submission to the off-site
CVS repository, and he wants to do this once a week.  My only
problem with this is that, even when I am the only programmer in
a project, I prefer to keep a finer-grained version control than
is possible with weekly submissions to the repository.

It occurs to me, though, that maybe I could set up a "personal"
CVS repository off my home directory (although I'll readily admit
that I've never set up a CVS repository of *any* kind before); I
would use it for my "fine-grain" version control, while submitting
new, boss-approved stuff to the "real" off-site repository only
once a week...

My knowledge of CVS is very limited; I know a few commands, and I
never deviate from the most basic functionality.  This "personal"
repository idea is far more "adventurous" than anything I've done
with CVS before.  That said, I have not found CVS to be terribly
flexible in the past, which is probably more a reflection of my
ignorance, than of CVS, but still I have to ask, how feasible is
this "personal repository" strategy? And if it is feasible at all,
how should I carry it out so as to facilitate the weekly submissions
to the off-site repository?


Thanks!

jill

-- 
To  s&e^n]d  me  m~a}i]l  r%e*m?o\v[e  bit from my a|d)d:r{e:s]s.