3 PATCHES - track and distribute your code changes
7 This page documents how to distribute your changes to GNU LilyPond
11 Distributing a change normally goes like this:
17 make your fix/add your code
25 e-mail your patch to one of the mailing lists
26 gnu-music-discuss@gnu.org or bug-gnu-music@gnu.org
27 (or if you're a bit shy, to the maintainer).
31 =head1 GENERATING A PATCH
33 In F<VERSION>, set TOPLEVEL_MY_PATCH_LEVEL:
37 TOPLEVEL_MY_PATCH_LEVEL = jcn1
39 In F<NEWS>, enter a summary of changes:
45 Then, from the top of Lily's source tree, type
47 make distclean # if you don't use --srcdir configure
50 which leaves your patch as F<./patch-0.1.48.jcn1>.
52 If you didn't configure Lily using --srcdir, you can do:
56 tar-ball: ../patches/patch-0.1.48.jcn1.gz
57 patch: ../patches/patch-0.1.48.jcn1.gz
58 updeet: ../test/updeet
62 For creating a patch you need
68 All items mentioned in F<INSTALL>. You're not going to send a patch
69 that you haven't even built, right?
77 Python (version 1.4 or newer).
78 You can of course make a patch by hand, which would go something like:
82 diff -urN lilypond-0.1.48 lilypond-0.1.48.jcn1 > patch-0.1.48.jcn1
84 but there are handy python scripts available. If you're doing development,
85 you'll need Python for other LilyPond scripts anyway.
89 The Lily directory structure, which looks like:
100 If you're not very quick with sending your patch, there's a good chance
101 that an new release of LilyPond comes available. In such a case (and
102 sometimes for other unkown reasons :-), the maintainer will probably ask
103 you to make a new patch against the latest release.
104 Your best bet is to download the latest release, and apply your patch
105 against this new source tree:
108 zpatch -p0 -E < ../patches/patch-0.1.48.jcn1.gz
110 Then, make a patch as shown above.
114 Han-Wen Nienhuys <hanwen@cs.ruu.nl>
116 Just keep on sending those patches!
119 PATCHES - track and distribute your code changes
123 This page documents how to distribute your changes to GNU LilyPond
127 Distributing a change normally goes like this:
133 make your fix/add your code
141 e-mail your patch to one of the mailing lists
142 gnu-music-discuss@gnu.org or bug-gnu-music@gnu.org
143 (or if you're a bit shy, to the maintainer).
147 =head1 GENERATING A PATCH
149 In F<VERSION>, set TOPLEVEL_MY_PATCH_LEVEL:
153 TOPLEVEL_MY_PATCH_LEVEL = jcn1
155 In F<NEWS>, enter a summary of changes:
161 Then, type something like
164 mv out/lilypond-0.1.48.jcn1.tar.gz ../releases
167 which leaves your patch as F<./patch-0.1.48.jcn1>.
173 tar-ball: ../patches/patch-0.1.48.jcn1.gz
174 patch: ../patches/patch-0.1.48.jcn1.gz
175 updeet: ../test/updeet
179 For creating a patch you need
185 All items mentioned in F<INSTALL>. You're not going to send a patch
186 that you haven't even built, right?
194 Python (version 1.4 or newer).
195 You can of course make a patch by hand, which would go something like:
199 diff -urN lilypond-0.1.48 lilypond-0.1.48.jcn1 > patch-0.1.48.jcn1
201 but there are handy python scripts available. If you're doing development,
202 you'll need Python for other LilyPond scripts anyway.
206 The Lily directory structure, which looks like:
217 If you're not very quick with sending your patch, there's a good chance
218 that an new release of LilyPond comes available. In such a case (and
219 sometimes for other unkown reasons :-), the maintainer will probably ask
220 you to make a new patch against the latest release.
221 Your best bet is to download the latest release, and apply your patch
222 against this new source tree:
225 zpatch -p0 -E < ../patches/patch-0.1.48.jcn1.gz
227 Then, make a patch as shown above.
231 Han-Wen Nienhuys <hanwen@cs.ruu.nl>
233 Just keep on sending those patches!