Graham Percival wrote:
On 29-Jun-05, at 1:03 AM, Han-Wen Nienhuys wrote:Log message: Branch lilypond_2_6 (MINOR_VERSION): go to 2.7.0Already? I thought that we'd work on 2.6.x for a while before branching 2.7.
Experience shows that it is really hard to make changes not break anything. So, we try not to change anything at all. This policy has worked really well for 2.4 and 2.2, IMHO.
Is there an easy way to apply changes to both branches? I imagine that the doc fixes for the next few weeks would apply to 2.6 as well as 2.7.
IMO the easiest most robust way is to edit the 2.6.0 -> 2.7.0 patch by hand, copying only the stable bits, and then apply that patch to the 2.6 branch.
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
