release: 1.1.47

[lilypond.git] / PATCHES.txt

diff --git a/PATCHES.txt b/PATCHES.txt
index af208e12f673752c18177a507b1e53f9adcef48d..55e1a71ea74b41882defb681f37b3a9d5e60feb6 100644 (file)
--- a/PATCHES.txt
+++ b/PATCHES.txt
@@ -6,11 +6,13 @@ NAME
 DESCRIPTION
 
      This  page  documents how to distribute your changes to
-GNU lilypond (or in fact any other StepMake package).
+GNU lilypond
 
 ABSTRACT
 
-     Distributing a change normally goes like this:
+     We would like to have unified context diffs  with  full
+pathnames.   A  script  automating supplied with Lily.  Dis-
+tributing a change normally goes like this:
 
 o    make your fix/add your code
 
@@ -119,11 +121,10 @@ 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 reasons  :-),
-the  maintainer  will  probably  ask you to make a new patch
-against the latest release.  Your best bet  is  to  download
-the  latest  release,  and apply your patch against this new
-source tree:
+In such a case, the maintainer will probably ask you to make
+a new patch against the latest release.  Your best bet is to
+download the latest release, and apply  your  patch  against
+this new source tree:
 
          cd lilypond-0.1.74
          gzip -dc ../patches/lilypond-0.1.73.jcn1.diff.gz | patch -p1 -E