2011/6/15 Graham Percival <[email protected]>: > Note that right now, there are no new translation patches in git > master.
This is because I've not merged lilypond/translation into master recently. I was unsure where to merge it into. > For that matter, Francisco should decide if he wants to keep > lilypond/translations merged with stable/2.14, or whether he wants > to merge it with master. Carl is managing translations of 2.14 by backporting some selected commits from lilypond/translation at my request. Only a few more translation commits will be done for 2.14 and will need to be backported from now on, so it has no sense to merge lilypond/translation into 2.14 now. Moreover, I periodically merge master into lilypond/translation, so our translation branch contains much 2.15 code. Only translation commits should be cherrypicked, not all code commits / history. Therefore, lilypond/translation branch will continue being merged into master. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
