Junio C Hamano <junkio@xxxxxxx> wrote:
> Jim Meyering <jim@xxxxxxxxxxxx> writes:
>> I'd like to develop using git, and have a commit hook mirror the
>> day-to-day changes (tags/commits) made in the git repo to a
>> cvs repository. The idea is that the only way changes get into
>> the cvs repo is via the git commit hook.
>
> I do not use the automated tools myself, but I sync the day-job
> work in my git repository to CVS at work. I do not develop with
> CVS but use it merely as a publishing medium. Although other
> people can make commits into CVS in which case I have to slurp
> the change back into my git repository.
>
> (0) Bootstrap. I did use git-cvsimport myself (this repository
...
> (1) Beginning of the day. In case other people did work on
...
Thank you for describing the process you use.
However, since I don't have to allow independent cvs commits,
I hope to bend git-cvsexportcommit to my needs.
It already does almost everything I want.
> using git-cvsimport), as I do not offhand know how exportcommit
> works. The commits on the git side you would want to push back
> are the ones on "master" but not on "origin", which you can get
> from "git rev-list origin..master", so I presume if you feed
> that to exportcommit things all magically work?
I haven't yet tried to restrict the mirroring to commits on a specific
git branch. So far, in the toy example I'm using to test things,
I have this in .git/hooks/post-commit:
#!/bin/sh
sha1_id=$(git-rev-parse --verify HEAD)
cvsdir=/var/tmp/work-c
cd $cvsdir && GIT_DIR=/var/tmp/git-experiment/work-g/.git \
git-cvsexportcommit -v -c -p $sha1_id
I'll clean up and post the changes I've made to git-cvsexportcommit
this week.
> By the way, I met Paul a few days ago and he mentioned that you
> have some quick audit results on our code from your evaluation.
> Can we expect fixes or at least pointing-out-problems from you
> sometime soon please?
I'll send one report separately.
-
: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html