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, type something like
48 mv out/lilypond-0.1.48.jcn1.tar.gz ../releases
51 which leaves your patch as F<./patch-0.1.48.jcn1>.
57 tar-ball: ../patches/patch-0.1.48.jcn1.gz
58 patch: ../patches/patch-0.1.48.jcn1.gz
59 updeet: ../test/updeet
63 For creating a patch you need
69 All items mentioned in F<INSTALL>. You're not going to send a patch
70 that you haven't even built, right?
78 Python (version 1.4 or newer).
79 You can of course make a patch by hand, which would go something like:
83 diff -urN lilypond-0.1.48 lilypond-0.1.48.jcn1 > patch-0.1.48.jcn1
85 but there are handy python scripts available. If you're doing development,
86 you'll need Python for other LilyPond scripts anyway.
90 The Lily directory structure, which looks like:
101 If you're not very quick with sending your patch, there's a good chance
102 that an new release of LilyPond comes available. In such a case (and
103 sometimes for other unkown reasons :-), the maintainer will probably ask
104 you to make a new patch against the latest release.
105 Your best bet is to download the latest release, and apply your patch
106 against this new source tree:
109 zpatch -p0 -E < ../patches/patch-0.1.48.jcn1.gz
111 Then, make a patch as shown above.
115 Han-Wen Nienhuys <hanwen@cs.ruu.nl>
117 Just keep on sending those patches!
120 PATCHES - track and distribute your code changes
124 This page documents how to distribute your changes to GNU LilyPond
128 Distributing a change normally goes like this:
134 make your fix/add your code
142 e-mail your patch to one of the mailing lists
143 gnu-music-discuss@gnu.org or bug-gnu-music@gnu.org
144 (or if you're a bit shy, to the maintainer).
148 =head1 GENERATING A PATCH
150 In F<VERSION>, set TOPLEVEL_MY_PATCH_LEVEL:
154 TOPLEVEL_MY_PATCH_LEVEL = jcn1
156 In F<NEWS>, enter a summary of changes:
162 Then, type something like
165 mv out/lilypond-0.1.48.jcn1.tar.gz ../releases
168 which leaves your patch as F<./patch-0.1.48.jcn1>.
174 tar-ball: ../patches/patch-0.1.48.jcn1.gz
175 patch: ../patches/patch-0.1.48.jcn1.gz
176 updeet: ../test/updeet
180 For creating a patch you need
186 All items mentioned in F<INSTALL>. You're not going to send a patch
187 that you haven't even built, right?
195 Python (version 1.4 or newer).
196 You can of course make a patch by hand, which would go something like:
200 diff -urN lilypond-0.1.48 lilypond-0.1.48.jcn1 > patch-0.1.48.jcn1
202 but there are handy python scripts available. If you're doing development,
203 you'll need Python for other LilyPond scripts anyway.
207 The Lily directory structure, which looks like:
218 If you're not very quick with sending your patch, there's a good chance
219 that an new release of LilyPond comes available. In such a case (and
220 sometimes for other unkown reasons :-), the maintainer will probably ask
221 you to make a new patch against the latest release.
222 Your best bet is to download the latest release, and apply your patch
223 against this new source tree:
226 zpatch -p0 -E < ../patches/patch-0.1.48.jcn1.gz
228 Then, make a patch as shown above.
232 Han-Wen Nienhuys <hanwen@cs.ruu.nl>
234 Just keep on sending those patches!