partial: 1.0.1.jcn

[lilypond.git] / Documentation / PATCHES.pod

diff --git a/Documentation/PATCHES.pod b/Documentation/PATCHES.pod
index 7fbc7480c0c6b2c9d76cfaa9f0a5e0e472e276d5..723bd87573960b680085bd404dc2b73fd7ee2ad7 100644 (file)
--- a/Documentation/PATCHES.pod
+++ b/Documentation/PATCHES.pod
@@ -18,13 +18,17 @@ make your fix/add your code
 
 =item *
 
+Add changes to NEWS, and add yourself to Documentation/AUTHORS.pod
+
+=item *
+
 generate a patch, 
 
 =item *
 
 e-mail your patch to one of the mailing lists
 gnu-music-discuss@gnu.org or bug-gnu-music@gnu.org
-(or if you're a bit shy, to the maintainer).
+
 
 =back
 
@@ -94,6 +98,20 @@ The Lily directory structure, which looks like:
 
 =back
        
+=head1 APPLYING PATCHES
+
+If you're following LilyPond development regularly, you probably want to
+download just the patch for each subsequent release.
+After downloading the patch (into the patches directory, of course), simply 
+apply it:
+
+    gzip -dc ../patches/patch-0.1.49.gz | patch -p1 -E
+
+and don't forget to make automatically generated files:
+
+    autoconf 1)
+    configure
+
 =head1 SYNCHRONISE
 
 If you're not very quick with sending your patch, there's a good chance
@@ -104,12 +122,17 @@ Your best bet is to download the latest release, and apply your patch
 against this new source tree:
 
     cd lilypond-0.1.49
-    zpatch -p0 -E < ../patches/patch-0.1.48.jcn1.gz
+    gzip -dc ../patches/patch-0.1.48.jcn1.gz | patch -p1 -E
+    autoconf 1)
+    configure
 
 Then, make a patch as shown above.
 
+1) patches don't include automatically generated files, i.e. F<configure>
+   and files generated by F<configure>.
+
 =head1 MAINTAINER
 
-Han-Wen Nienhuys <hanwen@cs.ruu.nl>
+Han-Wen Nienhuys <hanwen@cs.uu.nl>
 
 Just keep on sending those patches!