[Savannah-cvs] [654] add links to SavannahServices#vcs-rsync

[ineiev]

Revision: 654
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=654
Author:   ineiev
Date:     2023-09-08 03:59:15 -0400 (Fri, 08 Sep 2023)
Log Message:
-----------
add links to SavannahServices#vcs-rsync

Modified Paths:
--------------
    trunk/sviki/CvsRsyncWriteAccess.mdwn
    trunk/sviki/UsingVcs.mdwn

Modified: trunk/sviki/CvsRsyncWriteAccess.mdwn
===================================================================
--- trunk/sviki/CvsRsyncWriteAccess.mdwn        2023-09-08 07:41:10 UTC (rev 
653)
+++ trunk/sviki/CvsRsyncWriteAccess.mdwn        2023-09-08 07:59:15 UTC (rev 
654)
@@ -1,18 +1,18 @@
 # Rsync access to CVS repositories
 
-Since we provide rsync read-only access to the CVS repository, one may
-expect to also get write access. But we do not provide direct write
-access to the CVS repository for several reasons:
+Since we provide [[rsync read-only access|SavannahServices#vcs-rsync]]
+to the CVS repository, one may expect to also get write access.  But we
+do not provide direct write access to the CVS repository for several reasons:
 
--   integrity: changing or removing the history of a Savannah project
-    should be exceptional, and moderated. For example, in the event a
-    project goes proprietary, we would want to keep the repository of
-    the latest published free version available. Changing the history
+-   Integrity: changing or removing the history of a Savannah group
+    should be exceptional, and moderated.  For example, in the event a
+    package goes proprietary, we would want to keep the repository of
+    the latest published free version available.  Changing the history
     can also lead to situations where it's not clear who exactly sent a
     given commit.
--   security; we do not provide shell access to Savannah, so that users
+-   Security: we do not provide shell access to Savannah, so that users
     cannot send arbitrary commands to the system (fork bombs, twisted
-    calls to ptrace, many more). Granting CVS direct write access would
+    calls to ptrace, many more).  Granting CVS direct write access would
     provide a way
     to do so by creating a distinct CVSROOT/ directory. Such CVS root
     could also be used to trick CVS users into
@@ -26,13 +26,13 @@
     quite rare, just file a support request
 -   -x permissions changes: CVS doesn't support permissions, and
     recommands that you set permissions using installation scripts (such
-    as ./configure). CVS has a nasty `feature`, though, making a file
+    as ./configure).  CVS has a nasty `feature`, though, making a file
     executable if it is executable in the user working directory on
     first commit or import, without the ability to change that
-    permission later on. However, there is a discussion about providing
+    permission later on.  However, there is a discussion about providing
     a way to change this permission from the CVS client, so if you
     really want this feature you should contact the CVS team and
     possibly offer help for its inclusion in the very next release :)
 
 Last, if you want to work offline, we suggest you move to a different
-version control system. Savannah supports several.
+version control system.  Savannah supports several.

Modified: trunk/sviki/UsingVcs.mdwn
===================================================================
--- trunk/sviki/UsingVcs.mdwn   2023-09-08 07:41:10 UTC (rev 653)
+++ trunk/sviki/UsingVcs.mdwn   2023-09-08 07:59:15 UTC (rev 654)
@@ -15,6 +15,9 @@
 in "Developer tools" on the main page of the group, or "Use *VCS_name*"
 in the menu bar of the group.
 
+Additionally, we provide [[rsync read-only access|SavannahServices#vcs-rsync]]
+to the raw repository files.
+
 We generally don't remove existing repositories; when they are
 disabled, the group stops advertising them, but the repositories
 are still accessible.  Savannah admins can remove them from the server