1 <?xml version=
"1.0" encoding=
"UTF-8"?>
2 <!DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.1//EN"
3 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
4 <html xmlns=
"http://www.w3.org/1999/xhtml" xml:
lang=
"en">
6 <meta http-equiv=
"Content-Type" content=
"application/xhtml+xml; charset=UTF-8" />
7 <meta name=
"generator" content=
"AsciiDoc 10.2.0" />
8 <title>gitcvs-migration(
7)
</title>
9 <style type=
"text/css">
10 /* Shared CSS for AsciiDoc xhtml11 and html5 backends */
14 font-family: Georgia,serif;
18 h1, h2, h3, h4, h5, h6,
19 div.title, caption.title,
20 thead, p.table.header,
22 #author, #revnumber, #revdate, #revremark,
24 font-family: Arial,Helvetica,sans-serif;
28 margin:
1em
5%
1em
5%;
33 text-decoration: underline;
49 h1, h2, h3, h4, h5, h6 {
57 border-bottom:
2px solid silver;
77 border:
1px solid silver;
88 ul
> li { color: #aaa; }
89 ul
> li
> * { color: black; }
91 .monospaced, code, pre {
92 font-family:
"Courier New", Courier, monospace;
99 white-space: pre-wrap;
109 #revnumber, #revdate, #revremark {
114 border-top:
2px solid silver;
120 padding-bottom:
0.5em;
124 padding-bottom:
0.5em;
129 margin-bottom:
1.5em;
131 div.imageblock, div.exampleblock, div.verseblock,
132 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
133 div.admonitionblock {
135 margin-bottom:
1.5em;
137 div.admonitionblock {
139 margin-bottom:
2.0em;
144 div.content { /* Block element content. */
148 /* Block element titles. */
149 div.title, caption.title {
154 margin-bottom:
0.5em;
160 td div.title:first-child {
163 div.content div.title:first-child {
166 div.content + div.title {
170 div.sidebarblock
> div.content {
172 border:
1px solid #dddddd;
173 border-left:
4px solid #f0f0f0;
177 div.listingblock
> div.content {
178 border:
1px solid #dddddd;
179 border-left:
5px solid #f0f0f0;
184 div.quoteblock, div.verseblock {
188 border-left:
5px solid #f0f0f0;
192 div.quoteblock
> div.attribution {
197 div.verseblock
> pre.content {
198 font-family: inherit;
201 div.verseblock
> div.attribution {
205 /* DEPRECATED: Pre version
8.2.7 verse style literal block. */
206 div.verseblock + div.attribution {
210 div.admonitionblock .icon {
214 text-decoration: underline;
216 padding-right:
0.5em;
218 div.admonitionblock td.content {
220 border-left:
3px solid #dddddd;
223 div.exampleblock
> div.content {
224 border-left:
3px solid #dddddd;
228 div.imageblock div.content { padding-left:
0; }
229 span.image img { border-style: none; vertical-align: text-bottom; }
230 a.image:visited { color: white; }
234 margin-bottom:
0.8em;
247 list-style-position: outside;
250 list-style-type: decimal;
253 list-style-type: lower-alpha;
256 list-style-type: upper-alpha;
259 list-style-type: lower-roman;
262 list-style-type: upper-roman;
265 div.compact ul, div.compact ol,
266 div.compact p, div.compact p,
267 div.compact div, div.compact div {
269 margin-bottom:
0.1em;
281 margin-bottom:
0.8em;
284 padding-bottom:
15px;
286 dt.hdlist1.strong, td.hdlist1.strong {
292 padding-right:
0.8em;
298 div.hdlist.compact tr {
307 .footnote, .footnoteref {
311 span.footnote, span.footnoteref {
312 vertical-align: super;
316 margin:
20px
0 20px
0;
320 #footnotes div.footnote {
326 border-top:
1px solid silver;
335 padding-right:
0.5em;
336 padding-bottom:
0.3em;
344 #footer-badges { display: none; }
348 margin-bottom:
2.5em;
356 margin-bottom:
0.1em;
359 div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
376 span.aqua { color: aqua; }
377 span.black { color: black; }
378 span.blue { color: blue; }
379 span.fuchsia { color: fuchsia; }
380 span.gray { color: gray; }
381 span.green { color: green; }
382 span.lime { color: lime; }
383 span.maroon { color: maroon; }
384 span.navy { color: navy; }
385 span.olive { color: olive; }
386 span.purple { color: purple; }
387 span.red { color: red; }
388 span.silver { color: silver; }
389 span.teal { color: teal; }
390 span.white { color: white; }
391 span.yellow { color: yellow; }
393 span.aqua-background { background: aqua; }
394 span.black-background { background: black; }
395 span.blue-background { background: blue; }
396 span.fuchsia-background { background: fuchsia; }
397 span.gray-background { background: gray; }
398 span.green-background { background: green; }
399 span.lime-background { background: lime; }
400 span.maroon-background { background: maroon; }
401 span.navy-background { background: navy; }
402 span.olive-background { background: olive; }
403 span.purple-background { background: purple; }
404 span.red-background { background: red; }
405 span.silver-background { background: silver; }
406 span.teal-background { background: teal; }
407 span.white-background { background: white; }
408 span.yellow-background { background: yellow; }
410 span.big { font-size:
2em; }
411 span.small { font-size:
0.6em; }
413 span.underline { text-decoration: underline; }
414 span.overline { text-decoration: overline; }
415 span.line-through { text-decoration: line-through; }
417 div.unbreakable { page-break-inside: avoid; }
427 margin-bottom:
1.5em;
429 div.tableblock
> table {
430 border:
3px solid #
527bbd;
432 thead, p.table.header {
439 /* Because the table frame attribute is overridden by CSS in most browsers. */
440 div.tableblock
> table[
frame=
"void"] {
443 div.tableblock
> table[
frame=
"hsides"] {
444 border-left-style: none;
445 border-right-style: none;
447 div.tableblock
> table[
frame=
"vsides"] {
448 border-top-style: none;
449 border-bottom-style: none;
460 margin-bottom:
1.5em;
462 thead, p.tableblock.header {
473 border-color: #
527bbd;
474 border-collapse: collapse;
476 th.tableblock, td.tableblock {
480 border-color: #
527bbd;
483 table.tableblock.frame-topbot {
484 border-left-style: hidden;
485 border-right-style: hidden;
487 table.tableblock.frame-sides {
488 border-top-style: hidden;
489 border-bottom-style: hidden;
491 table.tableblock.frame-none {
492 border-style: hidden;
495 th.tableblock.halign-left, td.tableblock.halign-left {
498 th.tableblock.halign-center, td.tableblock.halign-center {
501 th.tableblock.halign-right, td.tableblock.halign-right {
505 th.tableblock.valign-top, td.tableblock.valign-top {
508 th.tableblock.valign-middle, td.tableblock.valign-middle {
509 vertical-align: middle;
511 th.tableblock.valign-bottom, td.tableblock.valign-bottom {
512 vertical-align: bottom;
523 padding-bottom:
0.5em;
524 border-top:
2px solid silver;
525 border-bottom:
2px solid silver;
530 body.manpage div.sectionbody {
535 body.manpage div#toc { display: none; }
540 <script type=
"text/javascript">
542 var asciidoc = { // Namespace.
544 /////////////////////////////////////////////////////////////////////
545 // Table Of Contents generator
546 /////////////////////////////////////////////////////////////////////
548 /* Author: Mihai Bazon, September
2002
549 * http://students.infoiasi.ro/~mishoo
551 * Table Of Content generator
554 * Feel free to use this script under the terms of the GNU General Public
555 * License, as long as you do not remove or alter this notice.
558 /* modified by Troy D. Hanson, September
2006. License: GPL */
559 /* modified by Stuart Rackham,
2006,
2009. License: GPL */
562 toc: function (toclevels) {
564 function getText(el) {
566 for (var i = el.firstChild; i != null; i = i.nextSibling) {
567 if (i.nodeType ==
3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
569 else if (i.firstChild != null)
575 function TocEntry(el, text, toclevel) {
578 this.toclevel = toclevel;
581 function tocEntries(el, toclevels) {
582 var result = new Array;
583 var re = new RegExp('[hH]([
1-'+(toclevels+
1)+'])');
584 // Function that scans the DOM tree for header elements (the DOM2
585 // nodeIterator API would be a better technique but not supported by all
587 var iterate = function (el) {
588 for (var i = el.firstChild; i != null; i = i.nextSibling) {
589 if (i.nodeType ==
1 /* Node.ELEMENT_NODE */) {
590 var mo = re.exec(i.tagName);
591 if (mo && (i.getAttribute(
"class") || i.getAttribute(
"className")) !=
"float") {
592 result[result.length] = new TocEntry(i, getText(i), mo[
1]-
1);
602 var toc = document.getElementById(
"toc");
607 // Delete existing TOC entries in case we're reloading the TOC.
608 var tocEntriesToRemove = [];
610 for (i =
0; i < toc.childNodes.length; i++) {
611 var entry = toc.childNodes[i];
612 if (entry.nodeName.toLowerCase() == 'div'
613 && entry.getAttribute(
"class")
614 && entry.getAttribute(
"class").match(/^toclevel/))
615 tocEntriesToRemove.push(entry);
617 for (i =
0; i < tocEntriesToRemove.length; i++) {
618 toc.removeChild(tocEntriesToRemove[i]);
621 // Rebuild TOC entries.
622 var entries = tocEntries(document.getElementById(
"content"), toclevels);
623 for (var i =
0; i < entries.length; ++i) {
624 var entry = entries[i];
625 if (entry.element.id ==
"")
626 entry.element.id =
"_toc_" + i;
627 var a = document.createElement(
"a");
628 a.href =
"#" + entry.element.id;
629 a.appendChild(document.createTextNode(entry.text));
630 var div = document.createElement(
"div");
632 div.className =
"toclevel" + entry.toclevel;
633 toc.appendChild(div);
635 if (entries.length ==
0)
636 toc.parentNode.removeChild(toc);
640 /////////////////////////////////////////////////////////////////////
641 // Footnotes generator
642 /////////////////////////////////////////////////////////////////////
644 /* Based on footnote generation code from:
645 * http://www.brandspankingnew.net/archive/
2005/
07/format_footnote.html
648 footnotes: function () {
649 // Delete existing footnote entries in case we're reloading the footnodes.
651 var noteholder = document.getElementById(
"footnotes");
655 var entriesToRemove = [];
656 for (i =
0; i < noteholder.childNodes.length; i++) {
657 var entry = noteholder.childNodes[i];
658 if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute(
"class") ==
"footnote")
659 entriesToRemove.push(entry);
661 for (i =
0; i < entriesToRemove.length; i++) {
662 noteholder.removeChild(entriesToRemove[i]);
665 // Rebuild footnote entries.
666 var cont = document.getElementById(
"content");
667 var spans = cont.getElementsByTagName(
"span");
670 for (i=
0; i
<spans.length; i++) {
671 if (spans[i].className ==
"footnote") {
673 var note = spans[i].getAttribute(
"data-note");
675 // Use [\s\S] in place of . so multi-line matches work.
676 // Because JavaScript has no s (dotall) regex flag.
677 note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[
1];
679 "[<a id='_footnoteref_" + n +
"' href='#_footnote_" + n +
680 "' title='View footnote' class='footnote'>" + n +
"</a>]";
681 spans[i].setAttribute(
"data-note", note);
683 noteholder.innerHTML +=
684 "<div class='footnote' id='_footnote_" + n +
"'>" +
685 "<a href='#_footnoteref_" + n +
"' title='Return to text'>" +
686 n +
"</a>. " + note +
"</div>";
687 var id =spans[i].getAttribute(
"id");
688 if (id != null) refs[
"#"+id] = n;
692 noteholder.parentNode.removeChild(noteholder);
694 // Process footnoterefs.
695 for (i=
0; i
<spans.length; i++) {
696 if (spans[i].className ==
"footnoteref") {
697 var href = spans[i].getElementsByTagName(
"a")[
0].getAttribute(
"href");
698 href = href.match(/#.*/)[
0]; // Because IE return full URL.
701 "[<a href='#_footnote_" + n +
702 "' title='View footnote' class='footnote'>" + n +
"</a>]";
708 install: function(toclevels) {
711 function reinstall() {
712 asciidoc.footnotes();
714 asciidoc.toc(toclevels);
718 function reinstallAndRemoveTimer() {
719 clearInterval(timerId);
723 timerId = setInterval(reinstall,
500);
724 if (document.addEventListener)
725 document.addEventListener(
"DOMContentLoaded", reinstallAndRemoveTimer, false);
727 window.onload = reinstallAndRemoveTimer;
735 <body class=
"manpage">
738 gitcvs-migration(
7) Manual Page
741 <div class=
"sectionbody">
742 <p>gitcvs-migration -
749 <h2 id=
"_synopsis">SYNOPSIS
</h2>
750 <div class=
"sectionbody">
751 <div class=
"verseblock">
752 <pre class=
"content"><em>git cvsimport
</em> *
</pre>
753 <div class=
"attribution">
758 <h2 id=
"_description">DESCRIPTION
</h2>
759 <div class=
"sectionbody">
760 <div class=
"paragraph"><p>Git differs from CVS in that every working tree contains a repository with
761 a full copy of the project history, and no repository is inherently more
762 important than any other. However, you can emulate the CVS model by
763 designating a single shared repository which people can synchronize with;
764 this document explains how to do that.
</p></div>
765 <div class=
"paragraph"><p>Some basic familiarity with Git is required. Having gone through
766 <a href=
"gittutorial.html">gittutorial(
7)
</a> and
767 <a href=
"gitglossary.html">gitglossary(
7)
</a> should be sufficient.
</p></div>
771 <h2 id=
"_developing_against_a_shared_repository">Developing against a shared repository
</h2>
772 <div class=
"sectionbody">
773 <div class=
"paragraph"><p>Suppose a shared repository is set up in /pub/repo.git on the host
774 foo.com. Then as an individual committer you can clone the shared
775 repository over ssh with:
</p></div>
776 <div class=
"listingblock">
777 <div class=
"content">
778 <pre><code>$ git clone foo.com:/pub/repo.git/ my-project
779 $ cd my-project
</code></pre>
781 <div class=
"paragraph"><p>and hack away. The equivalent of
<em>cvs update
</em> is
</p></div>
782 <div class=
"listingblock">
783 <div class=
"content">
784 <pre><code>$ git pull origin
</code></pre>
786 <div class=
"paragraph"><p>which merges in any work that others might have done since the clone
787 operation. If there are uncommitted changes in your working tree, commit
788 them first before running git pull.
</p></div>
789 <div class=
"admonitionblock">
792 <div class=
"title">Note
</div>
795 <div class=
"paragraph"><p>The
<em>pull
</em> command knows where to get updates from because of certain
796 configuration variables that were set by the first
<em>git clone
</em>
797 command; see
<code>git config -l
</code> and the
<a href=
"git-config.html">git-config(
1)
</a> man
798 page for details.
</p></div>
802 <div class=
"paragraph"><p>You can update the shared repository with your changes by first committing
803 your changes, and then using the
<em>git push
</em> command:
</p></div>
804 <div class=
"listingblock">
805 <div class=
"content">
806 <pre><code>$ git push origin master
</code></pre>
808 <div class=
"paragraph"><p>to
"push" those commits to the shared repository. If someone else has
809 updated the repository more recently,
<em>git push
</em>, like
<em>cvs commit
</em>, will
810 complain, in which case you must pull any changes before attempting the
811 push again.
</p></div>
812 <div class=
"paragraph"><p>In the
<em>git push
</em> command above we specify the name of the remote branch
813 to update (
<code>master
</code>). If we leave that out,
<em>git push
</em> tries to update
814 any branches in the remote repository that have the same name as a branch
815 in the local repository. So the last
<em>push
</em> can be done with either of:
</p></div>
816 <div class=
"listingblock">
817 <div class=
"content">
818 <pre><code>$ git push origin
819 $ git push foo.com:/pub/project.git/
</code></pre>
821 <div class=
"paragraph"><p>as long as the shared repository does not have any branches
822 other than
<code>master
</code>.
</p></div>
826 <h2 id=
"_setting_up_a_shared_repository">Setting Up a Shared Repository
</h2>
827 <div class=
"sectionbody">
828 <div class=
"paragraph"><p>We assume you have already created a Git repository for your project,
829 possibly created from scratch or from a tarball (see
830 <a href=
"gittutorial.html">gittutorial(
7)
</a>), or imported from an already existing CVS
831 repository (see the next section).
</p></div>
832 <div class=
"paragraph"><p>Assume your existing repo is at /home/alice/myproject. Create a new
"bare"
833 repository (a repository without a working tree) and fetch your project into
835 <div class=
"listingblock">
836 <div class=
"content">
837 <pre><code>$ mkdir /pub/my-repo.git
838 $ cd /pub/my-repo.git
839 $ git --bare init --shared
840 $ git --bare fetch /home/alice/myproject master:master
</code></pre>
842 <div class=
"paragraph"><p>Next, give every team member read/write access to this repository. One
843 easy way to do this is to give all the team members ssh access to the
844 machine where the repository is hosted. If you don
’t want to give them a
845 full shell on the machine, there is a restricted shell which only allows
846 users to do Git pushes and pulls; see
<a href=
"git-shell.html">git-shell(
1)
</a>.
</p></div>
847 <div class=
"paragraph"><p>Put all the committers in the same group, and make the repository
848 writable by that group:
</p></div>
849 <div class=
"listingblock">
850 <div class=
"content">
851 <pre><code>$ chgrp -R $group /pub/my-repo.git
</code></pre>
853 <div class=
"paragraph"><p>Make sure committers have a umask of at most
027, so that the directories
854 they create are writable and searchable by other group members.
</p></div>
858 <h2 id=
"_importing_a_cvs_archive">Importing a CVS archive
</h2>
859 <div class=
"sectionbody">
860 <div class=
"admonitionblock">
863 <div class=
"title">Note
</div>
865 <td class=
"content">These instructions use the
<code>git-cvsimport
</code> script which ships with
866 git, but other importers may provide better results. See the note in
867 <a href=
"git-cvsimport.html">git-cvsimport(
1)
</a> for other options.
</td>
870 <div class=
"paragraph"><p>First, install version
2.1 or higher of cvsps from
871 <a href=
"https://github.com/andreyvit/cvsps">https://github.com/andreyvit/cvsps
</a> and make
872 sure it is in your path. Then cd to a checked out CVS working directory
873 of the project you are interested in and run
<a href=
"git-cvsimport.html">git-cvsimport(
1)
</a>:
</p></div>
874 <div class=
"listingblock">
875 <div class=
"content">
876 <pre><code>$ git cvsimport -C
<destination
> <module
></code></pre>
878 <div class=
"paragraph"><p>This puts a Git archive of the named CVS module in the directory
879 <destination
>, which will be created if necessary.
</p></div>
880 <div class=
"paragraph"><p>The import checks out from CVS every revision of every file. Reportedly
881 cvsimport can average some twenty revisions per second, so for a
882 medium-sized project this should not take more than a couple of minutes.
883 Larger projects or remote repositories may take longer.
</p></div>
884 <div class=
"paragraph"><p>The main trunk is stored in the Git branch named
<code>origin
</code>, and additional
885 CVS branches are stored in Git branches with the same names. The most
886 recent version of the main trunk is also left checked out on the
<code>master
</code>
887 branch, so you can start adding your own changes right away.
</p></div>
888 <div class=
"paragraph"><p>The import is incremental, so if you call it again next month it will
889 fetch any CVS updates that have been made in the meantime. For this to
890 work, you must not modify the imported branches; instead, create new
891 branches for your own changes, and merge in the imported branches as
893 <div class=
"paragraph"><p>If you want a shared repository, you will need to make a bare clone
894 of the imported directory, as described above. Then treat the imported
895 directory as another development clone for purposes of merging
896 incremental imports.
</p></div>
900 <h2 id=
"_advanced_shared_repository_management">Advanced Shared Repository Management
</h2>
901 <div class=
"sectionbody">
902 <div class=
"paragraph"><p>Git allows you to specify scripts called
"hooks" to be run at certain
903 points. You can use these, for example, to send all commits to the shared
904 repository to a mailing list. See
<a href=
"githooks.html">githooks(
5)
</a>.
</p></div>
905 <div class=
"paragraph"><p>You can enforce finer grained permissions using update hooks. See
906 <a href=
"howto/update-hook-example.html">Controlling access to branches using
907 update hooks
</a>.
</p></div>
911 <h2 id=
"_providing_cvs_access_to_a_git_repository">Providing CVS Access to a Git Repository
</h2>
912 <div class=
"sectionbody">
913 <div class=
"paragraph"><p>It is also possible to provide true CVS access to a Git repository, so
914 that developers can still use CVS; see
<a href=
"git-cvsserver.html">git-cvsserver(
1)
</a> for
919 <h2 id=
"_alternative_development_models">Alternative Development Models
</h2>
920 <div class=
"sectionbody">
921 <div class=
"paragraph"><p>CVS users are accustomed to giving a group of developers commit access to
922 a common repository. As we
’ve seen, this is also possible with Git.
923 However, the distributed nature of Git allows other development models,
924 and you may want to first consider whether one of them might be a better
925 fit for your project.
</p></div>
926 <div class=
"paragraph"><p>For example, you can choose a single person to maintain the project
’s
927 primary public repository. Other developers then clone this repository
928 and each work in their own clone. When they have a series of changes that
929 they
’re happy with, they ask the maintainer to pull from the branch
930 containing the changes. The maintainer reviews their changes and pulls
931 them into the primary repository, which other developers pull from as
932 necessary to stay coordinated. The Linux kernel and other projects use
933 variants of this model.
</p></div>
934 <div class=
"paragraph"><p>With a small group, developers may just pull changes from each other
’s
935 repositories without the need for a central maintainer.
</p></div>
939 <h2 id=
"_see_also">SEE ALSO
</h2>
940 <div class=
"sectionbody">
941 <div class=
"paragraph"><p><a href=
"gittutorial.html">gittutorial(
7)
</a>,
942 <a href=
"gittutorial-2.html">gittutorial-
2(
7)
</a>,
943 <a href=
"gitcore-tutorial.html">gitcore-tutorial(
7)
</a>,
944 <a href=
"gitglossary.html">gitglossary(
7)
</a>,
945 <a href=
"giteveryday.html">giteveryday(
7)
</a>,
946 <a href=
"user-manual.html">The Git User
’s Manual
</a></p></div>
950 <h2 id=
"_git">GIT
</h2>
951 <div class=
"sectionbody">
952 <div class=
"paragraph"><p>Part of the
<a href=
"git.html">git(
1)
</a> suite
</p></div>
956 <div id=
"footnotes"><hr /></div>
958 <div id=
"footer-text">
960 2020-
03-
10 15:
02:
33 PDT