X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=PATCHES.txt;h=424a9b233257d6708cd1dc74467a1e0ea2e57840;hb=c844072722a39a5fcd20372b0497d9130bd41dd7;hp=6996afe212810904b0a0743f9a38cb13b2e8c52a;hpb=472c212541034e95c30f5a1a6bc99d7f36f15b68;p=lilypond.git

diff --git a/PATCHES.txt b/PATCHES.txt
index 6996afe212..424a9b2332 100644
--- a/PATCHES.txt
+++ b/PATCHES.txt
@@ -16,11 +16,13 @@ ABSTRACT
 
        o    make your fix/add your code
 
+       o    Add changes to NEWS, and add yourself to
+            Documentation/AUTHORS.pod
+
        o    generate a patch,
 
        o    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).
+            music-discuss@gnu.org or bug-gnu-music@gnu.org
 
 GENERATING A PATCH
        In VERSION, set TOPLEVEL_MY_PATCH_LEVEL:
@@ -56,12 +58,10 @@ PREREQUISITES
        o    All items mentioned in INSTALL.  You're not going to
             send a patch that you haven't even built, right?
 
-       o    GNU Diff
-
 
 
 
-20/Apr/98                LilyPond 0.1.58                        1
+12/May/98                LilyPond 0.1.63                        1
 
 
 
@@ -70,6 +70,8 @@ PREREQUISITES
 PATCHES(1)            LilyPond documentation           PATCHES(1)
 
 
+       o    GNU Diff
+
        o    Python (version 1.4 or newer).  You can of course
             make a patch by hand, which would go something like:
 
@@ -89,6 +91,20 @@ PATCHES(1)            LilyPond documentation           PATCHES(1)
                 test/
 
 
+       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
+
+
+SYNCHRONISE
        If you're not very quick with sending your patch, there's
        a good chance that an new release of LilyPond comes
        available.  In such a case (and sometimes for other unkown
@@ -98,12 +114,30 @@ PATCHES(1)            LilyPond documentation           PATCHES(1)
        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. configure
+          and files generated by configure.
+
+
+
+
+12/May/98                LilyPond 0.1.63                        2
+
+
+
+
+
+PATCHES(1)            LilyPond documentation           PATCHES(1)
+
+
 MAINTAINER
-       Han-Wen Nienhuys <hanwen@cs.ruu.nl>
+       Han-Wen Nienhuys <hanwen@cs.uu.nl>
 
        Just keep on sending those patches!
 
@@ -127,6 +161,38 @@ MAINTAINER
 
 
 
-20/Apr/98                LilyPond 0.1.58                        2
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+12/May/98                LilyPond 0.1.63                        3