[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [taler-deployment] branch master updated: roughly explain h
From: |
gnunet |
Subject: |
[GNUnet-SVN] [taler-deployment] branch master updated: roughly explain how gitolite is configured |
Date: |
Fri, 06 Oct 2017 15:45:49 +0200 |
This is an automated email from the git hooks/post-receive script.
marcello pushed a commit to branch master
in repository deployment.
The following commit(s) were added to refs/heads/master by this push:
new ab3b15f roughly explain how gitolite is configured
ab3b15f is described below
commit ab3b15f231fac50be793b5bab6ee9aad6b23396d
Author: Marcello Stanisci <address@hidden>
AuthorDate: Fri Oct 6 15:45:14 2017 +0200
roughly explain how gitolite is configured
---
doc/onboarding.texi | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/doc/onboarding.texi b/doc/onboarding.texi
index 0c9ccff..8840570 100644
--- a/doc/onboarding.texi
+++ b/doc/onboarding.texi
@@ -59,6 +59,16 @@ Texts. A copy of the license is included in the section
entitled
@node Taler.net
@section Taler.net
address@hidden Git
+
+Git at @code{taler.net} is managed by @emph{gitolite}. Creation and deletion
+of repositories, as well as users management, is done entirely by editing the
address@hidden file within the @code{gitolite-admin} repository.
+
+Please refer to gitolite official documentation, if more information is needed:
address@hidden://gitolite.com/gitolite/}.
+
+
This section documents the set-up of our main server @code{taler.net}.
@subsection Buildbot
--
To stop receiving notification emails like this one, please contact
address@hidden
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] [taler-deployment] branch master updated: roughly explain how gitolite is configured,
gnunet <=