From c7eef8c67c4340f306002afd65efaaeb9b4fff87 Mon Sep 17 00:00:00 2001
From: floam
Date: Mon, 20 Feb 2006 09:43:56 +0000
Subject: Use correct tag.
git-svn-id: svn://svn.icculus.org/quake3/trunk@560 edf5b092-35ff-0310-97b2-ce42778d08ea
---
web/include/help.php | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
(limited to 'web/include/help.php')
diff --git a/web/include/help.php b/web/include/help.php
index 4831c6e..83ae456 100644
--- a/web/include/help.php
+++ b/web/include/help.php
@@ -38,28 +38,28 @@ survival guide to generating patches.
not upstream, here is how you use it:
- Create a patch named amazing_new_feature.patch:
- svn diff > amazing_new_feature.patch
+ svn diff > amazing_new_feature.patch
- Apply a patch amazing_new_feature.patch:
- patch -p0 -i amazing_new_feature.patch
+ patch -p0 -i amazing_new_feature.patch
From a tarball or other release
If you didn't get the source code via SVN,
or for some reason that doesn't work for your situations, here's how to generate
- them using the tried-and-trusted diff tool between
+ them using the tried-and-trusted diff tool between
two files:
- Create a patch named amazing_new_feature.patch between oldfile and newfile:
- diff -u oldfile newfile > amazing_new_feature.patch
+ diff -u oldfile newfile > amazing_new_feature.patch
Create a patch named amazing_new_features.patch between directory olddir and newdir:
- diff -Naur olddir newdir > amazing_new_features.patch
+ diff -Naur olddir newdir > amazing_new_features.patch
Applying a patch is the same as with SVN, see above.
-For more information on diff, patch,
-and svn, read their respective man
-and info pages. For a more in-depth guide on Subversion take
+
For more information on diff, patch,
+and svn, read their respective man
+and info pages. For a more in-depth guide on Subversion take
a look at the SVN
Book.
--
cgit v1.2.3