X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=git-cvsexportcommit.html;h=a860342be20ece7167f1be52c1fbe417b9416468;hb=e246e3b880524446f9a269a00631d36a374eb63a;hp=ecaa05b391b801181003546365204e997fad498c;hpb=235a91e6b0d1d18a2517cf7e0a18278a6912bdb0;p=git.git diff --git a/git-cvsexportcommit.html b/git-cvsexportcommit.html index ecaa05b3..a860342b 100644 --- a/git-cvsexportcommit.html +++ b/git-cvsexportcommit.html @@ -278,7 +278,8 @@ git-cvsexportcommit(1) Manual Page

Exports a commit from GIT to a CVS checkout, making it easier to merge patches from a git repository into a CVS repository.

-

Execute it from the root of the CVS working copy. GIT_DIR must be defined.

+

Execute it from the root of the CVS working copy. GIT_DIR must be defined. +See examples below.

It does its best to do the safe thing, it will check that the files are unchanged and up to date in the CVS checkout, and it will not autocommit by default.

@@ -317,6 +318,34 @@ should the changeset be done against.

+

EXAMPLES

+
+
+
+Merge one patch into CVS +
+
+
+
+
$ export GIT_DIR=~/project/.git
+$ cd ~/project_cvs_checkout
+$ git-cvsexportcommit -v <commit-sha1>
+$ cvs commit -F .mgs <files>
+
+
+
+Merge pending patches into CVS automatically — only if you really know what you are doing +
+
+
+
+
$ export GIT_DIR=~/project/.git
+$ cd ~/project_cvs_checkout
+$ git-cherry cvshead myhead | sed -n 's/^+ //p' | xargs -l1 git-cvsexportcommit -c -p -v
+
+
+
+

Author

Written by Martin Langhoff <martin@catalyst.net.nz>

@@ -331,7 +360,7 @@ should the changeset be done against.