[Savannah-cvs] [670] minor updates

[ineiev]

Revision: 670
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=670
Author:   ineiev
Date:     2023-11-04 15:38:57 -0400 (Sat, 04 Nov 2023)
Log Message:
-----------
minor updates

Modified Paths:
--------------
    trunk/sviki/Git.mdwn

Modified: trunk/sviki/Git.mdwn
===================================================================
--- trunk/sviki/Git.mdwn        2023-10-29 01:00:05 UTC (rev 669)
+++ trunk/sviki/Git.mdwn        2023-11-04 19:38:57 UTC (rev 670)
@@ -3,7 +3,7 @@
 Current setup
 -------------
 
-Repositories are in `/srv/git/project_name.git` for now.
+Repositories are in `/srv/git/group_name.git` for now.
 git+ssh is supported in Savane's `sv_membersh` (delegates to git-shell).
 The git:// lightweight protocol is also available.
 
@@ -10,8 +10,8 @@
 Creating an additional repository
 ---------------------------------
 
-If a project wishes to have several repositories grouped together
-under the same project name.
+If a group wishes to have several repositories grouped together
+under the same group name.
 
 On vcs2, make a directory to place additional repositories:
 
@@ -37,8 +37,7 @@
     chown -R root:root /srv/git/lwip/lwip-contrib.git/hooks
     chmod -R og-w /srv/git/lwip/lwip-contrib.git/hooks
 
-This file is used as a fallback, group administrators can override it
-with a new description on
+Group administrators can edit repository description at
 `https://savannah.gnu.org/git/admin/?group=$unix_group_name`.
 
 Deprecated cvs server: If upon specific request add 'git-cvsserver'
@@ -73,8 +72,8 @@
 
     ln -s /usr/src/git-multimail/git-multimail/git_multimail.py hooks/
 
-Copy another projects template into the hooks directory and then edit
-it to configure it for the new project.  This can be done on the fly
+Copy the template from another group into the hooks directory and then
+edit it to configure it for the new group.  This can be done on the fly
 using sed.  This sets the Mail-Followup-To: header address to the
 devel discussion mailing list which is separate from the commit diff
 mailing list.  Set it to where follow-up discussion is desired.
@@ -140,7 +139,7 @@
 
 Verify the current and future state of the repository:
 
-    cd /srv/git/exampleproject.git
+    cd /srv/git/examplegroup.git
     git branch -l
     git log
     git log new-master
@@ -226,8 +225,8 @@
 -   Sub-repositories
 
 > -   We need to decide how to allow multiple repositories, or stick
->     with a single one. repo.or.cz seems to use `project_name.git` and
->     `project_name/forks.git`, which sounds cool.
+>     with a single one. repo.or.cz seems to use `group_name.git` and
+>     `group_name/forks.git`, which sounds cool.
 > -   repo.or.cz also implements the concept of "forks":
 >     <http://repo.or.cz/m/regproj.cgi?name=git/>
 >     which can be used to save bandwidth.