(Commit created by redmine exporter script from page "Organizational_Structure" versi...

[xonotic/xonotic.wiki.git] / Git.textile

diff --git a/Git.textile b/Git.textile
index 345b379512390eb9fd6a0a276069c1c160d3b822..ab671dd869bee1f746fdda52b49d0ed77974b6c7 100644 (file)
--- a/Git.textile
+++ b/Git.textile
@@ -1,11 +1,13 @@
+{{>toc}}
+
 h1. Git
 
-h2. After cloning the repository.
+h2. After cloning the repository
 
 After you cloned the repository (using <code>git clone <url></code>) you are ready to start creating a branch to start working.
-Please check [[Repository Access]] to make sure you checked out *all* of the repositories. <code>data/</code> for example resides in its own repo.
+Please check [[Repository Access]] to make sure you checked out *all* of the repositories. <code>data/</code> for example resides in its own repository.
 
-h2. "Did i mess up or is data/ of git.xonotic.org/xonotic.git actually empty?"
+h2. Project structure
 
 The game content can be divided into several distinct parts, like the <code>data/</code> directory, and some of its subdirectories. This is why there are several repositories, and a helper script to fetch and update them all. This is described in [[Repository Access]] under "Working with the helper script ./all"
 
@@ -18,9 +20,11 @@ The current structure looks as follows:
 |<code>/data/xonotic-music.pk3dir</code>|git://git.xonotic.org/xonotic/xonotic-music.pk3dir.git|
 |<code>/data/xonotic-nexcompat.pk3dir</code>|git://git.xonotic.org/xonotic/xonotic-nexcompat.pk3dir.git|
 
+When using the ssh protocol, the xonotic/ directory is skipped, so it's just: git.xonotic.org/xonotic.git
+
 You can still use the <code>data/</code> directory as base for the game since darkplaces now supports <code>.pk3dir</code> directories natively.
 
-h3. Creating a new branch:
+h2. Creating a new branch
 
 By convention, branches are usually called <yourname>/<branch>.
 Before creating a branch, you first have to choose a base of your branch. Then you can create your branch: