man pages section 1: User Commands

Exit Print View

Updated: July 2014

git-cvsexportcommit (1)


git-cvsexportcommit - Export a single commit to a CVS checkout


git cvsexportcommit [-h] [-u] [-v] [-c] [-P] [-p] [-a] [-d cvsroot]
[-w cvsworkdir] [-W] [-f] [-m msgprefix] [PARENTCOMMIT] COMMITID


Git Manual                                 GIT-CVSEXPORTCOMMIT(1)

     git-cvsexportcommit - Export a single commit to a CVS

     git cvsexportcommit [-h] [-u] [-v] [-c] [-P] [-p] [-a] [-d cvsroot]
             [-w cvsworkdir] [-W] [-f] [-m msgprefix] [PARENTCOMMIT] COMMITID

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

     Specify the name of a CVS checkout using the -w switch or
     execute it from the root of the CVS working copy. In the
     latter case 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.

     Supports file additions, removals, and commits that affect
     binary files.

     If the commit is a merge commit, you must tell git
     cvsexportcommit what parent the changeset should be done

         Commit automatically if the patch applied cleanly. It
         will not commit if any hunks fail to apply or there were
         other problems.

         Be pedantic (paranoid) when applying patches. Invokes
         patch with --fuzz=0

         Add authorship information. Adds Author line, and
         Committer (if different from Author) to the message.

         Set an alternative CVSROOT to use. This corresponds to
         the CVS -d parameter. Usually users will not want to set
         this, except if using CVS in an asymmetric fashion.

         Force the merge even if the files are not up to date.

Git          Last change: 02/22/2012                    1

Git Manual                                 GIT-CVSEXPORTCOMMIT(1)

         Force the parent commit, even if it is not a direct

         Prepend the commit message with the provided prefix.
         Useful for patch series and the like.

         Update affected files from CVS repository before
         attempting export.

         Reverse CVS keyword expansion (e.g. $Revision:$
         becomes $Revision$) in working CVS checkout before
         applying patch.

         Specify the location of the CVS checkout to use for the
         export. This option does not require GIT_DIR to be set
         before execution if the current directory is within a
         git repository. The default is the value of

         Tell cvsexportcommit that the current working directory
         is not only a Git checkout, but also the CVS checkout.
         Therefore, Git will reset the working directory to the
         parent commit before proceeding.


         The default location of the CVS checkout to use for the

     Merge one patch into CVS

             $ export GIT_DIR=~/project/.git
             $ cd ~/project_cvs_checkout
             $ git cvsexportcommit -v <commit-sha1>
             $ cvs commit -F .msg <files>

     Merge one patch into CVS (-c and -w options). The working
     directory is within the Git Repo

                     $ git cvsexportcommit -v -c -w ~/project_cvs_checkout <commit-sha1>

Git          Last change: 02/22/2012                    2

Git Manual                                 GIT-CVSEXPORTCOMMIT(1)

     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

     Part of the git(1) suite

     See attributes(5) for descriptions of the following

     |Availability   | developer/versioning/git |
     |Stability      | Uncommitted              |
     This software was built from source available at  The original
     community source was downloaded from  http://git-

     Further information about this software can be found on the
     open source community website at

Git          Last change: 02/22/2012                    3