| Re: [AD] Proposed documentation update |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Thu, Nov 14, 2002 at 08:50:35PM +0100, Grzegorz Adam Hankiewicz wrote:
> - adds brief instructions on how to create/submit patches.
> - updates mailing list/contact information.
Revising the previously applied patch I found three other mistakes
which I have fixed directly.
Index: docs/src/ahack._tx
===================================================================
RCS file: /cvsroot/alleg/allegro/docs/src/ahack._tx,v
retrieving revision 1.6
diff -u -r1.6 ahack._tx
--- docs/src/ahack._tx 16 Nov 2002 10:30:34 -0000 1.6
+++ docs/src/ahack._tx 17 Nov 2002 15:25:53 -0000
@@ -384,8 +384,7 @@
-@domain.hid
-Building your patch against an existent release
+@hnode Building your patch against an existent release
If you have obtained Allegro from an existent release, stable or unstable,
you will have all the source code contained in some archive format. You will
@@ -440,15 +439,14 @@
-@domain.hid
-Building your patch against a CVS version
+@hnode Building your patch against a CVS version
If you are working with the cvs version of Allegro which you can get from
Sourceforge (<link>http://sourceforge.net/projects/alleg/</a>), you won't need
to copy any files at all. Just modify the files you want, go to the root
directory of the cvs copy and type:
<textblock>
- diff -u > patch
+ cvs diff -u > patch
<endblock>
Unlike the standalone diff, the cvs diff command will work recursively
through the Allegro source tree, comparing each file against the Sourceforge