summaryrefslogtreecommitdiff
path: root/contributing/wiki.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'contributing/wiki.mdwn')
-rw-r--r--contributing/wiki.mdwn14
1 files changed, 7 insertions, 7 deletions
diff --git a/contributing/wiki.mdwn b/contributing/wiki.mdwn
index 25fb9911..7f70ae91 100644
--- a/contributing/wiki.mdwn
+++ b/contributing/wiki.mdwn
@@ -11,9 +11,9 @@ is included in the section entitled
(!) Some general hints first; they may sound very familiar from other software
projects:
-* Do independent changes *separately*: don't aggregate changes that don't
+ * Do independent changes *separately*: don't aggregate changes that don't
belong together.
-* Install your changes *early* and *often*: don't hold your contribution back
+ * Install your changes *early* and *often*: don't hold your contribution back
until you think it is perfect.
Before doing any changes, you are encouraged to play a bit in this wiki's
@@ -64,7 +64,7 @@ First, let's make sure that you're properly identifying yourself towards git.
Thomas Schwinge <tschwinge@gnu.org> 1186743435 +0200
If it doesn't look akin to that for you, you'd better adjust either your
-*EMAIL* environment variable or alternatively tell git about your real
+`EMAIL` environment variable or alternatively tell git about your real
identity:
$ git config --global user.name 'Your Name'
@@ -96,9 +96,9 @@ is also read-only.
$ git clone http://www.bddebian.com/git/wiki [dest]
-For all cases: if you omit *[dest]* it will default to *wiki*.
+For all cases: if you omit `[dest]` it will default to `wiki`.
-Later, you can just *cd* into the *wiki* directory and run a *git pull* to get
+Later, you can just `cd` into the `wiki` directory and run a `git pull` to get
hold of the latest changes others have been installing in the mean time.
@@ -150,7 +150,7 @@ If you can't do that, then first prepare to publish your changes:
0001-Be-a-bit-more-expressive.patch
[...]
-See through the generated **.patch* files and simply delete those you don't
+See through the generated `*.patch` files and simply delete those you don't
want to publish.
Finally, publish the good ones. If you have a local mail transfer agent
@@ -160,5 +160,5 @@ running, the following is all you have to do:
[...]
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
+the `*.patch` files to <web-hurd@gnu.org> or upload them somewhere for us to
download them from.