[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] [292] Git: markup language fixup
From: |
bob |
Subject: |
[Savannah-cvs] [292] Git: markup language fixup |
Date: |
Fri, 16 Dec 2016 21:00:07 +0000 (UTC) |
Revision: 292
http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=292
Author: rwp
Date: 2016-12-16 21:00:05 +0000 (Fri, 16 Dec 2016)
Log Message:
-----------
Git: markup language fixup
Modified Paths:
--------------
trunk/sviki/Git.mdwn
Modified: trunk/sviki/Git.mdwn
===================================================================
--- trunk/sviki/Git.mdwn 2016-12-16 20:59:57 UTC (rev 291)
+++ trunk/sviki/Git.mdwn 2016-12-16 21:00:05 UTC (rev 292)
@@ -3,8 +3,8 @@
Current setup
-------------
-Repositories are in /srv/git/project\_name.git for now.
-git+ssh is supported in Savane's sv\_membersh (delegates to git-shell).
+Repositories are in `/srv/git/project_name.git` for now.
+git+ssh is supported in Savane's `sv_membersh` (delegates to git-shell).
The git:// lightweight protocol is also available, check
/etc/xinetd.d/git.
@@ -201,8 +201,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 `project_name.git` and
+> `project_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.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Savannah-cvs] [292] Git: markup language fixup,
bob <=