Re: Invasive doc commit on lilypond/translation

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Invasive doc commit on lilypond/translation

Francisco Vila
2010/11/24 Valentin Villenave <[hidden email]>:

> Greetings translators, hi Paco,
>
> I've just pushed a potentially dangerous patch on the translations/
> branch (it doesn't break compiling here, though).
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=1b832d794f1444033f10465971e97d33f76fe310
>
> It does affect a *lot* of files (including in untranslated docs), so
> it might be a good idea to merge translations onto master quickly
> enough so that the English docs don't change too much in the meantime.
> I wouldn't merge it myself, but I've tried locally and it works
> AFAICS.

I have merged and am testing now.  Thanks for the advice,
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com


Reply | Threaded
Open this post in threaded view
|

Re: Invasive doc commit on lilypond/translation

Francisco Vila
2010/11/24 Francisco Vila <[hidden email]>:

> I have merged and am testing now.  Thanks for the advice,

Docs compile nicely after merge on master, pushed.

--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com