JehanneOS/newlib
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Change CVS->GIT in docs

Browse Source 
Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
This commit is contained in:
Corinna Vinschen 2015-03-10 14:19:42 +01:00
parent 09e300032f
commit 9272d8f942
3 changed files with 14 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
winsup/doc/ChangeLog
View File

@ -1,3 +1,8 @@
2015-03-10 Corinna Vinschen <corinna@vinschen.de>
* faq-programming.xml: Accommodate switch of Cygwin repo to GIT.
* setup-net.xml: Ditto.
2015-03-04 Corinna Vinschen <corinna@vinschen.de> 2015-03-04 Corinna Vinschen <corinna@vinschen.de>
* posix.xml (std-bsd): Add issetugid. * posix.xml (std-bsd): Add issetugid.

12
winsup/doc/faq-programming.xml
View File

@ -710,11 +710,11 @@ which requires the <literal>dblatex</literal>,
documentation, see the README included in the <literal>cygwin-doc</literal> package. documentation, see the README included in the <literal>cygwin-doc</literal> package.
</para> </para>
<para>Next, get the Cygwin source. Ideally, you should check out <para>Next, get the Cygwin source. Ideally, you should check out what you
what you need from CVS (<ulink url="https://cygwin.com/cvs.html"/>). This is the need from GIT (<ulink url="https://cygwin.com/git.html"/>). This is the
<emphasis>preferred method</emphasis> for acquiring the sources. Otherwise, if <emphasis>preferred method</emphasis> for acquiring the sources. Otherwise,
you are trying to duplicate a cygwin release then you should if you are trying to duplicate a cygwin release then you should download the
download the corresponding source package corresponding source package
(<literal>cygwin-x.y.z-n-src.tar.bz2</literal>). </para> (<literal>cygwin-x.y.z-n-src.tar.bz2</literal>). </para>
<para>You <emphasis>must</emphasis> build cygwin in a separate directory from <para>You <emphasis>must</emphasis> build cygwin in a separate directory from
@ -751,7 +751,7 @@ same time. Remove all but one.
symbols that you see in gdb are basically meaningless. It is also a good symbols that you see in gdb are basically meaningless. It is also a good
idea to use the latest code in case the bug has been fixed, so we idea to use the latest code in case the bug has been fixed, so we
recommend trying the latest snapshot from recommend trying the latest snapshot from
<ulink url="https://cygwin.com/snapshots/"/> or building the DLL from CVS. <ulink url="https://cygwin.com/snapshots/"/> or building the DLL from GIT.
</para> </para>
<para>To build a debugging version of the Cygwin DLL, you will need to follow <para>To build a debugging version of the Cygwin DLL, you will need to follow
the instructions at <ulink url="https://cygwin.com/faq/faq.html#faq.programming.building-cygwin"/>. the instructions at <ulink url="https://cygwin.com/faq/faq.html#faq.programming.building-cygwin"/>.

5
winsup/doc/setup-net.xml
View File

@ -34,8 +34,9 @@ The <command>setup.exe</command> installer is designed to be easy
for new users to understand while remaining flexible for the for new users to understand while remaining flexible for the
experienced. The volunteer development team is constantly working experienced. The volunteer development team is constantly working
on <command>setup.exe</command>; before requesting a new feature, on <command>setup.exe</command>; before requesting a new feature,
check the wishlist in the <ulink url="https://sourceware.org/cgi-bin/cvsweb.cgi/setup/README?cvsroot=cygwin-apps&amp;rev=2">CVS <literal>README</literal> check the wishlist in the
</ulink>. It may already be present in the CVS version! <ulink url="https://sourceware.org/git/gitweb.cgi?p=cygwin-setup.git;a=blob_plain;f=README;hb=HEAD">GIT <literal>README</literal>
</ulink>. It may already be present in the GIT version!
</para> </para>
<para> <para>