doc: git → contribute/git

wiki/src/bugs/exploitable_typo_in_url_regex__63__.mdwn

@@ -90,7 +90,7 @@ Many apologies if my English is unclear: please feel free to ask for clarificati
 >> stuff! :D Is the devel branch publicly available on some SVN
 >> somewhere or something?
 
->>> sure, see [[git]].
+>>> sure, see [[contribute/git]].
 
 >> I'd kinda like to doublecheck that the final regexes look good,
 

wiki/src/contribute.de.po

@@ -114,8 +114,8 @@ msgid "Tools"
 msgstr "Werkzeuge"
 
 #. type: Content of: <div><div><div><p>
-msgid "You can [[fetch Tails source code using git|git]]."
-msgstr "Sie können Sich [[den Tails source code über git zugänglich machen|git]]."
+msgid "You can [[fetch Tails source code using git|contribute/git]]."
+msgstr "Sie können Sich [[den Tails source code über git zugänglich machen|contribute/git]]."
 
 #. type: Content of: <div><div><div><p>
 msgid "This wiki is used as a basic bug tracking system:"

wiki/src/contribute.es.po

@@ -109,7 +109,7 @@ msgid "Tools"
 msgstr ""
 
 #. type: Content of: <div><div><div><p>
-msgid "You can [[fetch Tails source code using git|git]]."
+msgid "You can [[fetch Tails source code using git|contribute/git]]."
 msgstr ""
 
 #. type: Content of: <div><div><div><p>

wiki/src/contribute.fr.po

@@ -109,7 +109,7 @@ msgid "Tools"
 msgstr ""
 
 #. type: Content of: <div><div><div><p>
-msgid "You can [[fetch Tails source code using git|git]]."
+msgid "You can [[fetch Tails source code using git|contribute/git]]."
 msgstr ""
 
 #. type: Content of: <div><div><div><p>

wiki/src/contribute.html

@@ -68,7 +68,7 @@ Sorry about that.
 
 	<h1>Tools</h1>
 
-	<p>You can [[fetch Tails source code using git|git]].</p>
+	<p>You can [[fetch Tails source code using git|contribute/git]].</p>
 
 	<p>This wiki is used as a basic bug tracking system:</p>
 

wiki/src/contribute/design.mdwn

@@ -672,7 +672,7 @@ checked using OpenPGP detached signatures made with a key that is well
 linked to the web-of-trust.
 
 The sources are stored in a bunch of [Git](http://git-scm.com/)
-repositories. The [[git page|git]] on the Tails website provides all
+repositories. The [[git page|contribute/git]] on the Tails website provides all
 needed information to access these repositories.
 
 The latest version of this document can be found on the Tails
@@ -1134,7 +1134,7 @@ latest Debian stable release so there are not many problems.
 We intend to build and publish point releases (e.g.
 [[0.6.1|news/version_0.6.1]]) in a timely manner when security issues
 affect Tails. Such releases are based on the [[stable Git
-branch|/git]] and can thus also fix important — although not
+branch|contribute/git]] and can thus also fix important — although not
 security-related — bugs.
 
 ## 3.9 Hardware support

wiki/src/contribute/how/code.mdwn

@@ -114,7 +114,7 @@ unless you are sure it is really easy you should:
 
 # Hack
 
-Tails is developed using a set of [[Git repositories|git]]. You
+Tails is developed using a set of [[Git repositories|contribute/git]]. You
 probably want to base your work on the `devel` branch. If unsure, feel
 free to ask us.
 
@@ -156,7 +156,7 @@ Still here? Well, it seems you're not the
 Then you probably want to subscribe to the [tails-dev mailing
 list](https://boum.org/mailman/listinfo/tails-dev/). Maybe even
 subscribe to this website's RSS feed (see the [[recentchanges]] page)
-and/or track the Git commits (using [[our Gitweb|git]]'s RSS
+and/or track the Git commits (using [[our Gitweb|contribute/git]]'s RSS
 features). And probably read Tails [[specification and security design
 document|contribute/design]].
 

wiki/src/contribute/how/translate.mdwn

@@ -93,7 +93,7 @@ while custom Tails programs live in the `devel` branch.
 
 #### Send us Git patches
 
-1. Clone Tails [[Git repository|git]] onto your local system.
+1. Clone Tails [[Git repository|contribute/git]] onto your local system.
 2. Translate whatever you can in your preferred PO file editor. 
 3. Commit the changes you made to `.po` files.
 4. Use the `git format-patch` command to prepare patches.
@@ -102,7 +102,7 @@ while custom Tails programs live in the `devel` branch.
 
 #### Ask us to pull from your Git branch
 
-1. Setup your personal [[Git repository|git]]: if you already know
+1. Setup your personal [[Git repository|contribute/git]]: if you already know
    where to host it in a public place, this is great; or else [fork us
    on repo.or.cz](http://repo.or.cz/w/tails.git).
 2. Translate whatever you can in your preferred PO file editor. 

wiki/src/contribute/merge_policy.mdwn

@@ -5,7 +5,7 @@
 <p>New contributors can get started with the [[how to contribute code
 to Tails|contribute/how/code]] documentation.</p>
 
-<p>Tails is developed in a set of [[Git repositories|git]]. Slightly
+<p>Tails is developed in a set of [[Git repositories|contribute/git]]. Slightly
 different merge policies apply to contributors depending on their
 involvement level. On the other hand, some rules apply to anyone. This
 page documents both.</p>

wiki/src/index.es.po

@@ -185,8 +185,8 @@ msgstr "Vease [[Seguridad|Security]] para mas informacion."
 #~ "com/incognito/) y el  [Privatix Live-System](http://mandalka.name/"
 #~ "privatix/)"
 
-#~ msgid "with [[git]]"
-#~ msgstr "con [[git]]"
+#~ msgid "with [[contribute/git]]"
+#~ msgstr "con [[contribute/git]]"
 
 #~ msgid "One can also [[download]] pre-built images."
 #~ msgstr "Uno tambien puede [[descargar|download]] imagenes pre-compiladas."

wiki/src/patch.de.po

@@ -30,7 +30,7 @@ msgstr ""
 #. type: Plain text
 msgid ""
 "If your patch is non-trivial and might need several iterations to get right, "
-"please consider publishing a [[git]] branch."
+"please consider publishing a [[contribute/git]] branch."
 msgstr ""
 
 #. type: Plain text

wiki/src/patch.es.po

@@ -30,7 +30,7 @@ msgstr ""
 #. type: Plain text
 msgid ""
 "If your patch is non-trivial and might need several iterations to get right, "
-"please consider publishing a [[git]] branch."
+"please consider publishing a [[contribute/git]] branch."
 msgstr ""
 
 #. type: Plain text

wiki/src/patch.fr.po

@@ -34,10 +34,10 @@ msgstr ""
 #. type: Plain text
 msgid ""
 "If your patch is non-trivial and might need several iterations to get right, "
-"please consider publishing a [[git]] branch."
+"please consider publishing a [[contribute/git]] branch."
 msgstr ""
 "Si votre patch est compliqué et risque de demander plusieurs itérations avant\n"
-"d'être apllicable, envisagez de publier une branche [[git]]."
+"d'être apllicable, envisagez de publier une branche [[contribute/git]]."
 
 #. type: Plain text
 #, no-wrap

wiki/src/patch.mdwn

@@ -5,7 +5,7 @@ If you post a patch to the [[todo]] or [[bugs]] list, or elsewhere,
 once it's ready to be applied, add a 'patch' tag so it will show up here.
 
 If your patch is non-trivial and might need several iterations to get
-right, please consider publishing a [[git]] branch.
+right, please consider publishing a [[contribute/git]] branch.
 
 [[!inline pages="(todo/* or bugs/*) and link(patch)
 and !link(bugs/done) and !link(todo/done) and !tagged(todo/done)

wiki/src/todo.mdwn

@@ -11,7 +11,7 @@ instead.</p>
 <ul>
 <li>Newcomers wanting to get involved should start with the
   [[how to contribute|contribute]] documentation.</li>
-<li>Todo items that are fixed in Tails [[development branch|git]] and
+<li>Todo items that are fixed in Tails [[development branch|contribute/git]] and
   will therefore be solved in the next stable release appear on the
   [[list of pending todo items|todo/pending]].</li>
 <li>Todo items that have been solved in a shipped release appear on

wiki/src/todo/erase_memory_on_shutdown.mdwn

@@ -57,7 +57,7 @@ against Cold Boot Attacks.
 >>> upstream dev.
 >>> 
 >>>> This patch lives in the `feature/smem` branch of our own
->>>> `live-initramfs` [[git]] repository.
+>>>> `live-initramfs` [[contribute/git]] repository.
 >>>> 
 >>>> Our current solution works nicely, thus tagging `done`.
 >>>>>