release: 1.2.3

[lilypond.git] / Documentation / topdocs / PATCHES.yo

diff --git a/Documentation/topdocs/PATCHES.yo b/Documentation/topdocs/PATCHES.yo
index b08b7ea4287dce23799d54188addcca15bfcf9fa..eee04b313b9566f794da5c6acd48162b190d4706 100644 (file)
--- a/Documentation/topdocs/PATCHES.yo
+++ b/Documentation/topdocs/PATCHES.yo
@@ -5,15 +5,18 @@ PATCHES - track and distribute your code changes
 nsect(DESCRIPTION)
 
 This page documents how to distribute your changes to GNU lilypond
-(or in fact any other StepMake package).
 
 nsect(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.
+
+ Distributing a change normally
+goes like this:
 
 itemize(
 it()make your fix/add your code 
-it()Add changes to NEWS, and add yourself to Documentation/AUTHORS.yo
+it()Add changes to NEWS, and add yourself to Documentation/topdocs/AUTHORS.yo
 it()generate a patch, 
 it()e-mail your patch to one of the mailing lists
     gnu-music-discuss@gnu.org or bug-gnu-music@gnu.org
@@ -108,12 +111,11 @@ verb(
 
 nsect(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:
+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, 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:
 
 verb(
     cd lilypond-0.1.74