]>
Commit | Line | Data |
---|---|---|
5e0306ad | 1 | git-cvsexportcommit(1) |
79f6ac77 | 2 | ====================== |
5e0306ad ML |
3 | |
4 | NAME | |
5 | ---- | |
6 | git-cvsexportcommit - Export a commit to a CVS checkout | |
7 | ||
8 | ||
9 | SYNOPSIS | |
10 | -------- | |
353ce815 | 11 | 'git-cvsexportcommmit' [-h] [-v] [-c] [-p] [PARENTCOMMIT] COMMITID |
5e0306ad ML |
12 | |
13 | ||
14 | DESCRIPTION | |
15 | ----------- | |
16 | Exports a commit from GIT to a CVS checkout, making it easier | |
17 | to merge patches from a git repository into a CVS repository. | |
18 | ||
19 | Execute it from the root of the CVS working copy. GIT_DIR must be defined. | |
20 | ||
21 | It does its best to do the safe thing, it will check that the files are | |
22 | unchanged and up to date in the CVS checkout, and it will not autocommit | |
23 | by default. | |
24 | ||
25 | Supports file additions, removals, and commits that affect binary files. | |
26 | ||
27 | If the commit is a merge commit, you must tell git-cvsapplycommit what parent | |
28 | should the changeset be done against. | |
29 | ||
30 | OPTIONS | |
31 | ------- | |
32 | ||
33 | -c:: | |
34 | Commit automatically if the patch applied cleanly. It will not | |
35 | commit if any hunks fail to apply or there were other problems. | |
36 | ||
37 | -p:: | |
38 | Be pedantic (paranoid) when applying patches. Invokes patch with | |
39 | --fuzz=0 | |
40 | ||
41 | -v:: | |
42 | Verbose. | |
43 | ||
44 | Author | |
45 | ------ | |
46 | Written by Martin Langhoff <martin@catalyst.net.nz> | |
47 | ||
48 | Documentation | |
49 | -------------- | |
50 | Documentation by Martin Langhoff <martin@catalyst.net.nz> | |
51 | ||
52 | GIT | |
53 | --- | |
54 | Part of the gitlink:git[7] suite | |
55 |