Re: (patch) extremely minor changes to input/

[Graham Percival]

On Mon, 30 Sep 2002 00:55:03 +0200
Rune Zedeler <address@hidden> wrote:
> I think that in situations like this, the correct solution would be to 
> alter the patch-level of the lilypond-version - to i.e. 1.6.4.jr1 and 
> then use this as the required version for the input files.
> After 1.6.5 pops out you could (along with your next patch) also change 
> the requirements of you old files from 1.6.4.jr1 to 1.6.5.
> 
> Other suggestions?

- ask that your patch only be applied just before releasing a new version.
(ie apply patch requiring 1.6.5 and then release 1.6.5).  Disadvantage: no
testing of new patch.
- send in the patch to the code, but don't send in the patches to
documentation/examples.  When 1.6.5 is released and the new code works,
then send in the new examples which requrie 1.6.5/
- send a patch to the maillist (but not for inclusion in the main CVS tree)
that disables/deletes/modifies the examples which require 1.6.5 so that they
don't require it.  (basically, the patch I sent out)

Cheers,
- Graham