table of contents
- bookworm 1:2.39.2-1.1
- testing 1:2.45.2-1
- unstable 1:2.45.2-1.2
- experimental 1:2.45.2+next.20240614-1
GIT-CVSEXPORTCOMMIT(1) | Git Manual | GIT-CVSEXPORTCOMMIT(1) |
NAME¶
git-cvsexportcommit - Export a single commit to a CVS checkout
SYNOPSIS¶
git cvsexportcommit [-h] [-u] [-v] [-c] [-P] [-p] [-a] [-d <cvsroot>]
[-w <cvs-workdir>] [-W] [-f] [-m <msgprefix>] [<parent-commit>] <commit-id>
DESCRIPTION¶
Exports a commit from Git to a CVS checkout, making it easier to merge patches from a Git repository into a CVS repository.
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 against.
OPTIONS¶
-c
-p
-a
-d
-f
-P
-m
-u
-k
-w
-W
-v
CONFIGURATION¶
cvsexportcommit.cvsdir
EXAMPLES¶
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>
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
GIT¶
Part of the git(1) suite
06/16/2024 | Git 2.45.2.753.g447d99 |