summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2007-10-03 15:55:08 +0200
committerThomas Schwinge <tschwinge@gnu.org>2007-10-03 15:55:08 +0200
commit5801fc713dbb949a94eb49ce7fdd891b598b3f64 (patch)
treea90ef68d5c3e40a513a82d807b1ce92db1b77e24
parentcb158c34a866326658f54011e8fe77e0ef1bce23 (diff)
No native git protocol at the moment.
-rw-r--r--HowToContributeToThisWiki.mdwn10
1 files changed, 8 insertions, 2 deletions
diff --git a/HowToContributeToThisWiki.mdwn b/HowToContributeToThisWiki.mdwn
index 4086ed77..886c965d 100644
--- a/HowToContributeToThisWiki.mdwn
+++ b/HowToContributeToThisWiki.mdwn
@@ -36,7 +36,7 @@ Consult the git documentation about how to shuffle around with branches, how to
rename files, how to upload arbitrary data files, and so on.
(!) Before attempting any bigger editing work (to which you are sincerely
-invited!) be sure to check the involved pages' *Discussion* subpages (linked
+invited!) be sure to check the involved pages' *Discussion* subpages (linked
from the pages' header line) and in there take down (short) notes about the
editing endeavors you're going to undertake. Doing so should help to (a) avoid
double work and (b) avoid merge conflict if you install your changes into the
@@ -67,11 +67,17 @@ ssh configuration as advised on that page.) If you have an account on there:
If you don't have such an account or don't have your login data handy, you can
still get the pages the read-only way.
+Getting the files by using the native git protocol is currently not possible,
+but will be possible again as soon as the master repository has been relocated
+to the GNU Savannah machine.
+
+<!--
$ git clone git://flubber.bddebian.com/git/wiki [dest]
If that also doesn't work out, you have yet another chance: pull over the http
protocol. Not very efficient (read: rather inefficient), but it works. This
is also read-only.
+-->
$ git clone http://www.bddebian.com/git/wiki [dest]
@@ -138,6 +144,6 @@ running, the following is all you have to do:
$ git-send-email --to web-hurd@gnu.org *.patch
[...]
-If you don't have an mta running, you'll have to find another way: either post
+If you don't have an MTA running, you'll have to find another way: either post
the **.patch* files to <web-hurd@gnu.org> or upload them somewhere for us to
download them from.