Ensuring all git commits make it back to CVS when using git-cvs

Posted by Eric on Stack Overflow See other posts from Stack Overflow or by Eric
Published on 2010-03-11T19:21:02Z Indexed on 2010/03/11 19:24 UTC
Read the original article Hit count: 630

Filed under:
|

I'm using git-cvs, and my general workflow is something like this:

...write some code...
$ git commit
$ git cvsexportcommit -c -p -v <asdf>
$ git cvs-import $CVSROOT
$ git pull

This generally works fine for pushing my commits back to the CVS server and keeping things in sync. However, I'm wondering how I will realize that something is missing if I happen to do the "git commit" but forget to export it to the CVS server.

Is there a reasonable way to get a diff between my git repository and the CVS server, so I would know that something hadn't been committed all the way through? Or perhaps there's a better method of doing this altogether?

© Stack Overflow or respective owner

Related posts about git

Related posts about git-cvs