release: 0.1.60

[lilypond.git] / Documentation / PATCHES.pod

diff --git a/Documentation/PATCHES.pod b/Documentation/PATCHES.pod
index 7fbc7480c0c6b2c9d76cfaa9f0a5e0e472e276d5..45089c039f0b2f54dc7f0fb3c2c472db528b23bf 100644 (file)
--- a/Documentation/PATCHES.pod
+++ b/Documentation/PATCHES.pod
@@ -94,6 +94,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,10 +118,15 @@ 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>