git-cvsserver man page needs examples...

[david.hagood@gmail.com]

I'm trying to work out how I can use git-cvsserver on a local repository
to allow a stupid program that only understands CVS to work.

I've looked over the man page, but it really isn't clear as to what the
command lines and settings would look like. There seems to be a lot of
assumptions in the man page that aren't spelled out, such as the
assumption that you are making a repo available to many other hosts.

There is the tantalizing hint that "you can rename git-cvsserver to cvs"
which would lead me to believe that I might just be able to point the
stupid program at git-cvsserver and be done with it, but that doesn't
really seem clear.

It also isn't clear what effect operations on the repo, such as "git
checkout", would have on the view that the CVS client sees - if any at
all.

Then there is the statement "You also need to ensure that each repository
is "bare" (without a git index file) for cvs commit to work." Does that
mean that I have to have a repository that operates differently for CVS
commit to work than a standard repository for local use?

Might I suggest that the man page either contain or point to some examples
of using git-cvsserver for different use cases, such as:

local repo and server, for stupid programs that speak CVS but not GIT.
local repo and server exporting to other workstations.

I haven't found any good examples on-line of how to achieve these goals -
just reiterations of the man pages.