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:
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
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:
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
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!
-20/Apr/98 LilyPond 0.1.58 2
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+12/May/98 LilyPond 0.1.63 3