Remove most other references to CVS, replace with git and GitHub

This commit is contained in:
Mark Komarinski 2016-02-02 11:10:25 -05:00
parent fbfdd772f0
commit f78f52cff1
5 changed files with 10 additions and 9 deletions

View File

@ -44,9 +44,9 @@
<section id="fix-own">
<title>Fixing Your Own Documents</title>
<para>If you find an error in your own document, please fix it and re-submit the document. You can re-submit your files by emailing them to <email>submit@en.tldp.org</email>. </para>
<para>If you find an error in your own document, please fix it and re-submit the document. If you do not have GitHub access, you can send an e-mail to <email>discuss@en.tldp.org</email> with notification that you have changes and a volunteer will work with you to handle the change. </para>
<para>If you have been using the CVS, you can submit your changes to the CVS tree and then send a note to the submit mailing list (<email>submit@en.tldp.org</email>). In your email please give the exact path of your document in the CVS tree.</para>
<para>If you are using GitHub, you can commit your changes to your local repository and then generate a pull request to have it added to the central repository.</para>
<para>Remember to update the revision history at the top of the document.</para>
</section>

View File

@ -12,14 +12,14 @@
<para>
As part of the review process a Review Coordinator will add your
document to the CVS (including any associated image files) and
document to the git repository (including any associated image files) and
notify the submit mailing list that your document is ready for
publication.
</para>
<para>
Subsequent updates to your document can be made via the CVS. Please read
<xref linkend="cvs" /> for more information.
Subsequent updates to your document can be made via git if you like. Please read
<xref linkend="git" /> for more information.
</para>
<!--

View File

@ -11,7 +11,7 @@
<para>This document uses the following conventions<footnote>
<para>Please, take a look at the <ulink
url="http://cvsview.tldp.org/index.cgi/LDP/guide/docbook/LDP-Author-Guide/">
url="https://raw.githubusercontent.com/tLDP/LDP/master/LDP/guide/docbook/LDP-Author-Guide/LDP-Author-Guide.xml">
source</ulink> to see how to get
similar results on your documents. You should also remember that
the way this appears to you depends on the format in which you are reading

View File

@ -95,7 +95,7 @@
The GFDL (GNU Free Documentation License) is available in XML format
at <ulink url="http://www.gnu.org/licenses/fdl.xml">http://www.gnu.org/licenses/fdl.xml</ulink>. For a version in appendix format suitable for including
in your document, you can see get the XML for this document
from CVS at <ulink url="http://cvsview.tldp.org/index.cgi/LDP/guide/docbook/LDP-Author-Guide/fdl-appendix.xml">http://cvsview.tldp.org/index.cgi/LDP/guide/docbook/LDP-Author-Guide/fdl-appendix.xml</ulink>.
from GitHub at <ulink url="https://raw.githubusercontent.com/tLDP/LDP/master/LDP/guide/docbook/LDP-Author-Guide/fdl-appendix.xml">https://raw.githubusercontent.com/tLDP/LDP/master/LDP/guide/docbook/LDP-Author-Guide/fdl-appendix.xml</ulink>.
</para>
<para>
TLDP template files for DocBook (XML and SGML) and Linuxdoc SGML are

View File

@ -6,8 +6,9 @@
<para>
The LDP uses a number of scripts to distribute your document.
These scripts submit your document to the LDP's CVS (a free
document version management system), and then they transform your document to other formats that
These scripts retrieve your document from the LDP's document
version management system (currently git using GitHub), and
then they transform your document to other formats that
users then read. Your document will also be mirrored on a number
of sites worldwide (yet another set of scripts).
</para>