new repository

1 files changed, 12 insertions, 0 deletions

diff --git a/devdocs/git/git-cvsexportcommit.html b/devdocs/git/git-cvsexportcommit.html
new file mode 100644
index 00000000..d8692081
--- /dev/null
+++ b/devdocs/git/git-cvsexportcommit.html
@@ -0,0 +1,12 @@
+<h1>git-cvsexportcommit</h1>  <h2 id="_name">Name</h2> <div class="sectionbody">  <p>git-cvsexportcommit - Export a single commit to a CVS checkout</p>  </div>   <h2 id="_synopsis">Synopsis</h2> <div class="sectionbody"> <div class="verseblock"> <pre class="content" data-language="shell">git cvsexportcommit [-h] [-u] [-v] [-c] [-P] [-p] [-a] [-d &lt;cvsroot&gt;]
+        [-w &lt;cvs-workdir&gt;] [-W] [-f] [-m &lt;msgprefix&gt;] [&lt;parent-commit&gt;] &lt;commit-id&gt;</pre> </div> </div>   <h2 id="_description">Description</h2> <div class="sectionbody">  <p>Exports a commit from Git to a CVS checkout, making it easier to merge patches from a Git repository into a CVS repository.</p>   <p>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.</p>   <p>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.</p>   <p>Supports file additions, removals, and commits that affect binary files.</p>   <p>If the commit is a merge commit, you must tell <code>git cvsexportcommit</code> what parent the changeset should be done against.</p>  </div>   <h2 id="_options">Options</h2> <div class="sectionbody"> <div class="dlist"> <dl> <dt class="hdlist1" id="Documentation/git-cvsexportcommit.txt--c"> -c </dt> <dd> <p>Commit automatically if the patch applied cleanly. It will not commit if any hunks fail to apply or there were other problems.</p> </dd> <dt class="hdlist1" id="Documentation/git-cvsexportcommit.txt--p"> -p </dt> <dd> <p>Be pedantic (paranoid) when applying patches. Invokes patch with --fuzz=0</p> </dd> <dt class="hdlist1" id="Documentation/git-cvsexportcommit.txt--a"> -a </dt> <dd> <p>Add authorship information. Adds Author line, and Committer (if different from Author) to the message.</p> </dd> <dt class="hdlist1" id="Documentation/git-cvsexportcommit.txt--d"> -d </dt> <dd> <p>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.</p> </dd> <dt class="hdlist1" id="Documentation/git-cvsexportcommit.txt--f"> -f </dt> <dd> <p>Force the merge even if the files are not up to date.</p> </dd> <dt class="hdlist1" id="Documentation/git-cvsexportcommit.txt--P"> -P </dt> <dd> <p>Force the parent commit, even if it is not a direct parent.</p> </dd> <dt class="hdlist1" id="Documentation/git-cvsexportcommit.txt--m"> -m </dt> <dd> <p>Prepend the commit message with the provided prefix. Useful for patch series and the like.</p> </dd> <dt class="hdlist1" id="Documentation/git-cvsexportcommit.txt--u"> -u </dt> <dd> <p>Update affected files from CVS repository before attempting export.</p> </dd> <dt class="hdlist1" id="Documentation/git-cvsexportcommit.txt--k"> -k </dt> <dd> <p>Reverse CVS keyword expansion (e.g. $Revision: 1.2.3.4$ becomes $Revision$) in working CVS checkout before applying patch.</p> </dd> <dt class="hdlist1" id="Documentation/git-cvsexportcommit.txt--w"> -w </dt> <dd> <p>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 <code>cvsexportcommit.cvsdir</code>.</p> </dd> <dt class="hdlist1" id="Documentation/git-cvsexportcommit.txt--W"> -W </dt> <dd> <p>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.</p> </dd> <dt class="hdlist1" id="Documentation/git-cvsexportcommit.txt--v"> -v </dt> <dd> <p>Verbose.</p> </dd> </dl> </div> </div>   <h2 id="_configuration">Configuration</h2> <div class="sectionbody"> <div class="dlist"> <dl> <dt class="hdlist1" id="Documentation/git-cvsexportcommit.txt-cvsexportcommitcvsdir"> cvsexportcommit.cvsdir </dt> <dd> <p>The default location of the CVS checkout to use for the export.</p> </dd> </dl> </div> </div>   <h2 id="_examples">Examples</h2> <div class="sectionbody"> <div class="dlist"> <dl> <dt class="hdlist1" id="Documentation/git-cvsexportcommit.txt-MergeonepatchintoCVS"> Merge one patch into CVS </dt> <dd> <div class="listingblock"> <div class="content"> <pre data-language="shell-session">$ export GIT_DIR=~/project/.git
+$ cd ~/project_cvs_checkout
+$ git cvsexportcommit -v &lt;commit-sha1&gt;
+$ cvs commit -F .msg &lt;files&gt;</pre> </div> </div> </dd> <dt class="hdlist1" id="Documentation/git-cvsexportcommit.txt-MergeonepatchintoCVS-cand-woptionsTheworkingdirectoryiswithintheGitRepo"> Merge one patch into CVS (-c and -w options). The working directory is within the Git Repo </dt> <dd> <div class="listingblock"> <div class="content"> <pre>        $ git cvsexportcommit -v -c -w ~/project_cvs_checkout &lt;commit-sha1&gt;</pre> </div> </div> </dd> <dt class="hdlist1" id="Documentation/git-cvsexportcommit.txt-MergependingpatchesintoCVSautomatically820182128201onlyifyoureallyknowwhatyouaredoing"> Merge pending patches into CVS automatically — only if you really know what you are doing </dt> <dd> <div class="listingblock"> <div class="content"> <pre data-language="shell-session">$ export GIT_DIR=~/project/.git
+$ cd ~/project_cvs_checkout
+$ git cherry cvshead myhead | sed -n 's/^+ //p' | xargs -l1 git cvsexportcommit -c -p -v</pre> </div> </div> </dd> </dl> </div> </div><div class="_attribution">
+  <p class="_attribution-p">
+    &copy; 2012&ndash;2024 Scott Chacon and others<br>Licensed under the MIT License.<br>
+    <a href="https://git-scm.com/docs/git-cvsexportcommit" class="_attribution-link">https://git-scm.com/docs/git-cvsexportcommit</a>
+  </p>
+</div>