[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNU-traductores] gnudist:/home/www/html/server/standards/README.savanna
|
From: |
gnudist's file diff daemon |
|
Subject: |
[GNU-traductores] gnudist:/home/www/html/server/standards/README.savannah.html -- recent changes |
|
Date: |
Wed, 12 Dec 2001 07:33:56 -0800 (PST) |
This is an automated report from gnudist.
Recent changes to /home/www/html/server/standards/README.savannah.html:
71 -rw-rw-r-- 1 webcvs www 71423 Dec 11 11:36
/home/www/html/server/standards/README.savannah.html
diff -u
/home/diffmon/old_file_dir/gnudist:!home!www!html!server!standards!README.savannah.html.gz
/home/www/html/server/standards/README.savannah.html
--- /tmp/diffmon24364 Wed Dec 12 07:33:56 2001
+++ /home/www/html/server/standards/README.savannah.html Tue Dec 11
11:36:46 2001
@@ -1,16 +1,16 @@
-<html lang="en"><head>
+<html lang="en">
+<head>
<title>`Savannah'</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name=description content="`Savannah'">
-<meta name=generator content="makeinfo 4.0">
+<meta name=generator content="makeinfo 4.0b">
<link href="http://texinfo.org/"; rel=generator-home>
-</head><body>
+</head>
+<body>
<p><hr>
Node:<a name="Top">Top</a>,
-Next:<a rel=next href="#Introduction">Introduction</a>,
-Previous:<a rel=previous href="#(dir)">(dir)</a>,
-Up:<a rel=up href="#(dir)">(dir)</a>
+Next:<a rel=next href="#Introduction">Introduction</a>
<br>
<h1>Savannah</h1>
@@ -20,7 +20,7 @@
<a href="http://savannah.gnu.org/";>Savannah</a> is a <a
href="http://www.sourceforge.net";>SourceForge</a>
clone based on the
<a
href="http://download.sourceforge.net/alexandria/SF2_0.tar.gz";>SourceForge-2.0</a>
-software. It is dedicated the GNU projects.
+software. It is dedicated to Free Software projects.
<p>Because of the highly specific nature of the software, Savannah is a
fork of the SourceForge-2.0 software. Attempting to make it modular and
@@ -42,7 +42,6 @@
<li><a href="#Mailman">Mailman</a>:
<li><a href="#Mails%20and%20aliases">Mails and aliases</a>:
<li><a href="#Unlock%20alias%20at%20gnu.org%20account">Unlock alias at gnu.org
account</a>:
-<li><a href="#Migration">Migration</a>:
<li><a href="#Users%20and%20CVS%20synchronization">Users and CVS
synchronization</a>:
<li><a href="#Publishing%20this%20document">Publishing this document</a>:
<li><a href="#System%20Administration">System Administration</a>:
@@ -93,7 +92,7 @@
<h1>Introduction</h1>
-<p>Savannah currently provides the CVS frontend. Check the <a
href="http://savannah.gnu.org/pm/task.php?group_project_id=1&group_id=11&func=browse";>Task
List</a> for details on planned developments.
+<p>Savannah currently provides the CVS frontend. Check the <a
href="http://savannah.gnu.org/docs/savannah-plan.html";>Development Plan</a> for
information on the future.
<p>Setting up Savannah is not an easy task because it has to integrate existing
habits and projects without breaking anything. However, the <a
href="http://www.zoy.org/~guillaum/SF/";>SourceForge Installation Guide</a> by
@@ -143,7 +142,7 @@
su -
export CVS_RSH=ssh
cd /subversions/sourceforge/src/savannah
-cvs -q update
+cvs -q -z3 update
</pre>
<p><hr>
@@ -155,8 +154,12 @@
<h1>Savannah Administrator</h1>
-<p>At a given time only one person can be in charge of approving or rejecting
projects submitted to Savannah. The /admin/ interface is not fit for concurrent
access. The user assigned to this task is the one in charge. It is his
-responsibility to find someone else before leaving :-)
+<p>At a given time only one person can be in charge of approving or
+rejecting projects submitted to Savannah. The /admin/ interface is not
+fit for concurrent access. The user assigned to this task is the one in
+charge. It is his responsibility to find someone else before leaving :-)
+People currently (Dec 2001) playing this role are
+<a href="mailto:address@hidden";>Jaime E. Villate</a>, <a
href="mailto:address@hidden";>Guillaume Morin</a> and <a
href="mailto:address@hidden";>Loic Dachary</a>.
<p>The task
<a
href="https://savannah.gnu.org/pm/task.php?func=detailtask&project_task_id=54&group_id=11&group_project_id=30";>current
administrator</a>
@@ -218,10 +221,8 @@
<p>For each project registered on Savannah there may be two CVS repositories.
One to store the sources of the project and one to store the web of the
-project. The sources repository is in /subversions/cvs/software and the
-web repository is in /webcvs. The /webcvs symbolic link
-points to /webcvs and the /cvsroot symbolic link points to
-/subversions/cvs/software.
+project. The sources repository is in /cvsroot and the
+web repository is in /webcvs.
<ul>
<li><a href="#Import%20repositories">Import repositories</a>:
@@ -265,9 +266,9 @@
<h2>Sources CVS repositories</h2>
<p>When a project has a license that is not <code>website</code> a source
-repository is created under /subversions/cvs/software/project with
+repository is created under /cvsroot/project with
a private CVSROOT that only contains anoncvs. The developers of the
-project have access to the CVSROOT directory.
+project have write access to the CVSROOT directory.
<p>The group <code>project</code> is created to grant write access to the
repository
to all the members of the project.
@@ -278,10 +279,11 @@
<p>If the <code>html_cvs</code> field for a given Savannah project is empty, it
is not associated with a part of the webcvs repository.
-<p>It allows them to add commit notification by doing the following,
-replacing <code>project</code> with the name of their project:
+<p>A project member may add commit notification by doing the following:
+(replace <code>project</code> with the name of the project and
<code>user</code> by
+the Savannah login name).
-<pre>cvs -d subversions.gnu.org:/cvsroot/project co CVSROOT
+<pre>cvs -d address@hidden:/cvsroot/project co CVSROOT
In CVSROOT/commitinfo
@@ -295,10 +297,9 @@
<p>The email address must exist, it will not be automatically generated.
<p>For compatibility with the cvs setup before Savannah was introduced,
-/subversions/cvs/common contains repositories that existed before Savannah.
-When a project is registered in Savannah, a symbolic link is created
-(/subversions/cvs/software/project/project) that points to the already
-existing /subversions/cvs/common/project directory.
+/subversions/cvs/common contains symbolic links to the corresponding
+Savannah directory. Developers are encourage to stop using this
+historical setup.
<p>The /cvs symbolic link points to /subversions/cvs/common so that people
already using it to access their repositories can continue to do so. Before
@@ -316,10 +317,10 @@
<h2>Source CVS tarbals</h2>
<p>The sf_backup script builds tarbals for each repository in the
-/subversions/cvs/software directory. Those tarbals are stored in
+/cvsroot directory. Those tarbals are stored in
the /subversions/cvs/software.backups directory and linked with the
savannah.gnu.org:/cvs.backups URL. The tarbals are generated daily,
-only if at least one file in the repository is more recent than the
+if at least one file in the repository is more recent than the
tarbal.
<p><hr>
@@ -333,10 +334,10 @@
<p>When a project has an <code>html_cvs</code> field that is not empty in the
<code>group</code> table, a web repository is created in
-/webcvs/<code>html_cvs</code>. By default the <code>html_cvs</code>
-field has the value <code>/software/project/</code> but it may be edited with
-the savannah.gnu.org/admin/. See the gnujobs, greve and bravegw projects
-for examples.
+/webcvs/<code>html_cvs</code>. By default the <code>html_cvs</code> field has
the
+value <code>/software/project/</code> but it may be edited by the Savannah
+administrators at the savannah.gnu.org/admin/ URL. Project members may
+not change this value. See the gnujobs and gdb projects for examples.
<p>If a project is tagged as non-gnu (gnu field in table groups set to N)
it is given a space in the /non-gnu/project directory instead.
@@ -350,7 +351,7 @@
<p>The group <code>webproject</code> is created to grant write access to the
repository
to all the members of the project.
-<p>All the www.gnu.org web was imported in /webcvs.
+<p>All the www.gnu.org web was imported in /webcvs (early 2001).
When a project is registered on Savannah and there already exists
a directory for it in the repository (either .../software/project or
the value of the <code>html_cvs</code> field), a chgrp -R webproject is done
@@ -360,7 +361,8 @@
<p>The <code>www</code> project in Savannah is treated in a special way. All
the
members of the <code>www</code> project have access to the whole repository
in /webcvs. It means that they are always included in every
<code>webproject</code>
-created.
+created. However, the non-gnu projects and not included and webmasters may
+not modify them if they are not a member of the group.
<p><hr>
Node:<a name="Web%20CVS%20Symbolic%20links">Web CVS Symbolic links</a>,
@@ -386,8 +388,7 @@
<code>.symlinks</code> files, prepend a <code>ln -s</code> in front of each
line
and execute them. Well, in reality it's not that simple but you get
the idea. The <code>.symlinks</code> file can only be used to control the
-symbolic link in the directory where they are. File names with / will
-be ignored.
+symbolic link in the directory where they are.
<p><hr>
Node:<a name="Sync%20of%20www.gnu.org%20on%20commit">Sync of www.gnu.org on
commit</a>,
@@ -404,9 +405,9 @@
web repository.
<p>The /subversions/sourceforge/src/savannah/gnuscripts/sf_www_sync.c
-program was derived from the /usr/local/bin/webcvs.c program. It is
-called on each commit to keep the www.gnu.org web site in sync with
-the CVS repository.
+program was derived from the /usr/local/bin/webcvs.c program (now
+obsolete). It is called on each commit to keep the www.gnu.org web site
+in sync with the CVS repository.
<p>The idea is to runs a cvs update -l (to prevent recursion) in the
directory where the commit was done. Since the command will be called
@@ -452,7 +453,7 @@
repository only. For instance the <code>bravegw</code> Savannah project only
give write access to the /webcvs/brave-gnu-world part of the repository.
-<p>A project bound to a specific subdirectory will grante write access to
+<p>A project bound to a specific subdirectory will grant write access to
all the tree under this subdirectory. There is no way, for instance,
to grant write access to group B to /webcvs/thispart and write access
to group A to /webcvs/thispart/subdir. If you do this group B win and
@@ -523,7 +524,7 @@
from the Savannah database into the <code>savannah.gnu.org/savannah.xml</code>
file.
<p>In addition a dump containing information that users may not want to
-publish to the public such as email and ssh keys is built in
+publish to the public such as email and ssh public keys is built in
<code>/subversions/sourceforge/dumps/savannah.xml</code>. The command line
<pre>sf_xml --private
@@ -662,17 +663,16 @@
</dl>
-<p>It is possible to generate files specific to a given target machine
-quite easily. For instance the <code>account-fsffr.txt</code> file is a
+<p>It is possible to generate files specific to a given target machine.
+For instance the <code>account-fsffr.txt</code> file is a
selection of the users that are members of the
<a href="http://savannah.gnu.org/projects/fsffr/";>fsffr</a> projects. The
<code>Makefile</code> in the dumps directory is responsible for the creation of
these files. It uses XSLT to select the relevant informations from the
<code>savannah.xml</code> dump.
-<p>Address all questions and requests to address@hidden and
-log <a href="https://savannah.gnu.org/support/?group_id=11";>support
requests</a> on
-the web.
+<p>Send all questions and requests to address@hidden or
+to <a href="https://savannah.gnu.org/support/?group_id=11";>support
requests</a>.
<p><hr>
Node:<a name="Mailman">Mailman</a>,
@@ -756,7 +756,7 @@
<p><hr>
Node:<a name="Unlock%20alias%20at%20gnu.org%20account">Unlock alias at gnu.org
account</a>,
-Next:<a rel=next href="#Migration">Migration</a>,
+Next:<a rel=next href="#Users%20and%20CVS%20synchronization">Users and CVS
synchronization</a>,
Previous:<a rel=previous href="#Mails%20and%20aliases">Mails and aliases</a>,
Up:<a rel=up href="#Top">Top</a>
<br>
@@ -774,104 +774,33 @@
</pre>
<p><hr>
-Node:<a name="Migration">Migration</a>,
-Next:<a rel=next href="#Users%20and%20CVS%20synchronization">Users and CVS
synchronization</a>,
-Previous:<a rel=previous
href="#Unlock%20alias%20at%20gnu.org%20account">Unlock alias at gnu.org
account</a>,
-Up:<a rel=up href="#Top">Top</a>
-<br>
-
-<h1>Migration</h1>
-
-<p>Must be root to run this script. You are advised to run it in
-/subversions/sourceforge/tmp, although it is not mandatory.
-
-<p>The <code>sf_migrate</code> script creates a Savannah project for an
existing project
-in the /subversions/cvs/common directory. It is done in three steps:
-
-<ul>
-<li>sf_migrate -add project | mysql sourceforge
-
-<li>sf_migrate -bind project | mysql sourceforge
-
-<li>sf_migrate -mail project
-</ul>
-
-<dl>
-<dt><code>--add</code>
-<dd>Will create the project in Savannah if it does not yet exists.
-It will also scan the /etc/passwd and /etc/group files and create
-users in Savannah.
-
-<p>When explaining the situation to a user added to Savannah in this
-way, one could say it like this. If you have a Kerberos account on
-gnu.org, use the same login and password on Savannah and change the
-password immediately afterwards: it will not change your Kerberos
-password, just the Savannah password. If you only have a pserver
-account, use the same login and password on Savannah. If you have
-both, use the Kerberos account login and password. If you have none
-and access CVS using SSH public keys, ask to address@hidden to
-give you a password. This last case requires human interaction to
-prevent someone from stealing your account name.
-
-<br><dt><code>--bind</code>
-<dd>Will bind the users created to the project. This cannot be done in
-one step (-add -bind) because of unique identifiers allocations by
-the MySQL database.
-
-<br><dt><code>--mail</code>
-<dd>Generate a Emacs-VM formated mail ready to send to all contributors
-of the project that explains what has been done.
-</dl>
-
-<p>When a user with SSH access thru public key was added by sf_migrate,
-she/he will be instructed to ask for a password to address@hidden
-The sf_pass script can be used to set her/his password. A mail must be sent
-by the user requesting the password with the encrypted password. Instruct
-the user to generate the password using the following command:
-
-<pre>perl -e 'print crypt("mypassword",
- join "", (".", "/", 0..9, "A".."Z", "a".."z")[rand 64, rand 64])'
-</pre>
-
-<p>When the user send the password crypted, set it using:
-
-<pre>sf_pass --set thename cryptpass | mysql sourceforge
-</pre>
-
-<p>After 24 hours, check user logged in and lock the user if it is not the
-case. This is to prevent obvious holes.
-
-<pre>sf_pass --unset thename | mysql sourceforge
-</pre>
-
-<p><hr>
Node:<a name="Users%20and%20CVS%20synchronization">Users and CVS
synchronization</a>,
Next:<a rel=next href="#Publishing%20this%20document">Publishing this
document</a>,
-Previous:<a rel=previous href="#Migration">Migration</a>,
+Previous:<a rel=previous
href="#Unlock%20alias%20at%20gnu.org%20account">Unlock alias at gnu.org
account</a>,
Up:<a rel=up href="#Top">Top</a>
<br>
<h1>Users and CVS synchronization</h1>
-<p>Must be root to run this script. Must export CVS_RSH=ssh. You are
-advised to run it in /subversions/sourceforge/tmp, although it is not
-mandatory.
+<p>Must be root to run this script and make sur you export CVS_RSH=ssh.
+You are advised to run it in /subversions/sourceforge/tmp, although it
+is not mandatory.
<p>It is run from the crontab and the output is logged in /var/log/sf_cvs.log.
-<p>The <code>sf_cvs</code> script generates a shell script that will
synchronize
+<p>The <code>sf_cvs</code> perl script generates a shell script that will
synchronize
the system files with the state of the Savannah database (sourceforge).
-<p>This script only generates lines if something needs to be done. When
-the resulting script is executed, another run <code>must not</code> display
-any action, unless the database was modified in the meantime.
+<p>This script only generates lines if something needs to be done. When the
+resulting script is executed, another run <code>must not</code> display any
+action (unless the database was modified in the meantime which is unlikely).
<p>It performs the following tasks, in this order.
<dl>
<br><dt><code>Add new projects</code>
-<dd>/subversions/cvs/software/project and /webcvs/software/project
+<dd>/cvsroot/project and /webcvs/software/project (or /webcvs/non-gnu/project)
directories are created.
<br><dt><code>Update existing projects</code>
@@ -879,7 +808,7 @@
directory or a directory with wrong permissions.
<br><dt><code>Add missing users</code>
-<dd>Create users (in /etc/passwd) that are bound to at least a project in
Savannah.
+<dd>Create users (in /etc/passwd) that are bound to at least one project in
Savannah.
<br><dt><code>Remove users</code>
<dd>Remove users not bound to any project in Savannah
@@ -892,20 +821,18 @@
<br><dt><code>Update the groups of anoncvs</code>
<dd>The list of groups (projects) to which anoncvs belongs is restricted
-by the public/non public status of a project. The only exception is
-emacs that is a public project without anonymous cvs access. When the
-policy changes the sf_cvs script will have to be updated.
+by the public/non public status of a project.
<br><dt><code>Update the CVS password file</code>
-<dd>Update the /subversions/cvs/CVSROOT/passwd file to reflect the
+<dd>Update the /cvs/CVSROOT/passwd file to reflect the
passwd and users bound to projects in Savannah.
<br><dt><code>Create download area for non-GNU projects</code>
<dd>A directory is created at /upload/projectname, only if the project
is not part of the GNU project.
-<br><dt><code>Update xinetd.conf</code>
-<dd>Update the cvspserver/cvskserver with all possible pserver roots
+<br><dt><code>Update cvs-pserver.conf</code>
+<dd>Update the list of all possible pserver roots.
</dl>
@@ -1033,6 +960,7 @@
7 6 * * * root sf_xml >
/subversions/sourceforge/src/savannah/www/savannah.xml
14 6 * * * root sf_xml --private >
/subversions/sourceforge/dumps/savannah.xml
30 6 * * * root make -s -C /subversions/sourceforge/dumps all
+0 */1 * * * root sf_xml --list >
/subversions/sourceforge/dumps/list.xml
#
# Daily web server statistics
# http://savannah.gnu.org/savannah.html#Web%20Usage%20Statistics
@@ -1049,14 +977,15 @@
<h2>Savannah logs</h2>
-<p>The logs of Savannah are in <code>/var/log</code>. They are rotated by the
-<code>/etc/logrotate.d/savannah</code> configuration file of logrotate.
+<p>The logs of the Savannah scripts are in <code>/var/log</code>. They are
+rotated by the <code>/etc/logrotate.d/savannah</code> configuration file of
+logrotate.
<dl>
<br><dt><code>/var/log/sf_cvs.log</code>
<dd>Modification of the the system files from the mysql database information
-so that CVS can work properly.
+so that CVS, upload etc can work properly.
<br><dt><code>/var/log/sf_sync_www.log</code>
<dd>Loginfo and update information generated by the sf_sync_www program.
@@ -1082,7 +1011,8 @@
<p>The MySQL installation is an exception that must be fixed. It is installed
with the /usr/local/mysql prefix. It was not installed from the debian
package because I (address@hidden) was not able to fix the MySQL-3.23
-package to make it work on potato.
+package to make it work on potato. Now that the machine runs woody, this
+historical hack should be removed.
<p><hr>
Node:<a name="NGROUPS_MAX">NGROUPS_MAX</a>,
@@ -1096,8 +1026,8 @@
<p>The large number of groups a user can have (>32) implies to modify
some basic programs (namely useradd and usermod).
-<p>Gordon Matzigkeit <address@hidden> modified
-/usr/local/src/cvs-1.10.8/src/server.c to overcome the limit builtin glibc.
+<p>The cvs-1.11.1p1 executable was patched and the patches are available
+at cvs-1.11.1p1-2001-12-11.patch.
<p>Here is the patch applied to /usr/local/src/shadow-19990827. The
modified usermod and useradd have been installed in
@@ -1657,15 +1587,14 @@
allows to power cycle the machine. More information on this subject
may be found in sysadmin.texi (http://savannah.gnu.org/projects/sysadmin/).
-<p>A full Debian installation was done on <code>/dev/hdb2</code> and can be
used if for
-some reason the installation is so corrupted that even a single boot
-will not work. This emergency installation is labeled as such in the
-grub menu.
+<p>A full Debian installation was done on <code>/dev/hdb2</code> and can be
used
+if the installation is so corrupted that even a single boot will not
+work. This emergency installation is labeled as such in the grub menu.
-<p>When booting on this emergency partition the file systems of the regular
+<p>When booting on the emergency partition, the file systems of the regular
installation are mounted under the <code>/subversions.gnu.org/</code>
directory.
-<p>The grub menu file (menu.lst) can is located on this partition, as explained
+<p>The grub menu file (menu.lst) is located on this partition, as explained
above.
<p><hr>
@@ -1760,13 +1689,11 @@
<li>Account Management with Savannah: <a href="#Account%20Management">Account
Management</a>
<li>accounts.txt access: <a href="#Account%20Management">Account Management</a>
<li>authorized_keys: <a href="#Account%20Management">Account Management</a>
-<li>Automatic migration: <a href="#Migration">Migration</a>
<li>backups of the database: <a href="#Database%20Backups">Database Backups</a>
<li>booting: <a href="#Booting%20with%20grub%20and%20not%20lilo">Booting with
grub and not lilo</a>
<li>change html_cvs value: <a href="#Web%20CVS%20repositories">Web CVS
repositories</a>
<li>CJN: <a href="#Skill%20List">Skill List</a>
<li>commit notification: <a href="#Sources%20CVS%20repositories">Sources CVS
repositories</a>
-<li>convert project to Savannah: <a href="#Migration">Migration</a>
<li>corrupted kernel or file system: <a
href="#Emergency%20situation">Emergency situation</a>
<li>crash recovery: <a href="#Emergency%20situation">Emergency situation</a>
<li>crontab: <a href="#Savannah%20crontab">Savannah crontab</a>
@@ -1808,14 +1735,17 @@
<li>Savannah project: <a href="#Installation">Installation</a>
<li>Savannah root directory: <a href="#Installation">Installation</a>
<li>savannah.xml access: <a href="#Account%20Management">Account Management</a>
-<li>sf_aliases: <a href="#Mails%20and%20aliases">Mails and aliases</a>
-<li>sf_backup: <a href="#Database%20Backups">Database Backups</a>, <a
href="#Source%20CVS%20tarbals">Source CVS tarbals</a>
+<li>sf_aliases: <a href="#Mails%20and%20aliases">Mails and aliases</a>, <a
href="#Installation">Installation</a>
+<li>sf_backup: <a href="#Database%20Backups">Database Backups</a>, <a
href="#Source%20CVS%20tarbals">Source CVS tarbals</a>, <a
href="#Installation">Installation</a>
<li>sf_cvs: <a href="#Users%20and%20CVS%20synchronization">Users and CVS
synchronization</a>, <a href="#Installation">Installation</a>
-<li>sf_migrate: <a href="#Migration">Migration</a>, <a
href="#Installation">Installation</a>
-<li>sf_pass: <a href="#Migration">Migration</a>, <a
href="#Installation">Installation</a>
-<li>sf_stat: <a href="#Web%20Usage%20Statistics">Web Usage Statistics</a>
-<li>sf_sync_www: <a href="#Sync%20of%20www.gnu.org%20on%20commit">Sync of
www.gnu.org on commit</a>
-<li>sf_www: <a href="#Web%20CVS%20and%20Projects">Web CVS and Projects</a>
+<li>sf_migrate: <a href="#Installation">Installation</a>
+<li>sf_non-gnu2gnu.sh: <a href="#Installation">Installation</a>
+<li>sf_pass: <a href="#Installation">Installation</a>
+<li>sf_skill: <a href="#Installation">Installation</a>
+<li>sf_stat: <a href="#Web%20Usage%20Statistics">Web Usage Statistics</a>, <a
href="#Installation">Installation</a>
+<li>sf_sync_www: <a href="#Sync%20of%20www.gnu.org%20on%20commit">Sync of
www.gnu.org on commit</a>, <a href="#Installation">Installation</a>
+<li>sf_www: <a href="#Web%20CVS%20and%20Projects">Web CVS and Projects</a>, <a
href="#Installation">Installation</a>
+<li>sf_xml: <a href="#Installation">Installation</a>
<li>skill: <a href="#Skill%20List">Skill List</a>
<li>SourceForge: <a href="#Top">Top</a>
<li>SourceForge fork rationale: <a href="#Top">Top</a>
@@ -1880,7 +1810,6 @@
</ul>
<li><a href="#Mails%20and%20aliases">Mails and aliases</a>
<li><a href="#Unlock%20alias%20at%20gnu.org%20account">Unlock alias at gnu.org
account</a>
-<li><a href="#Migration">Migration</a>
<li><a href="#Users%20and%20CVS%20synchronization">Users and CVS
synchronization</a>
<li><a href="#Publishing%20this%20document">Publishing this document</a>
<li><a href="#System%20Administration">System Administration</a>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNU-traductores] gnudist:/home/www/html/server/standards/README.savannah.html -- recent changes,
gnudist's file diff daemon <=