| Re: [translations] how to handle snippets commit if you don't have push access |
[ Thread Index |
Date Index
| More lilynet.net/translations Archives
]
- To: Federico Bruni <fedelogy@xxxxxxxxx>
- Subject: Re: [translations] how to handle snippets commit if you don't have push access
- From: Francisco Vila <paconet.org@xxxxxxxxx>
- Date: Mon, 30 Jan 2012 09:24:11 +0100
- Cc: LilyPond Translation <translations@xxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=J1bhG2L2tGh2F5i5DgMCYCpuVLZ0iwCezpfLuZA208E=; b=Iaum4IzO2Dy7wlcz2WnbGiki51uygcaQSwey4wNw3bxQpV6lvUG/JlYbTxEXBBO8fI OSLL3YqT0HuF4OKh9U9ENInHV2jJJ39tIK8dbyOzlrULUltV8DzeBZrEq+j/5w+Y5J+r 8f7G8EiNfo41m2fPkWev704i8gWwNGwjKmrks=
2012/1/30 Francisco Vila <paconet.org@xxxxxxxxx>:
> Undoubtedly there is something wrong in this all. Whoever changes its
> own texidoc and runs makelsr.py forces all other translators to update
> their own committish in texidocs, which in turn forces them to run
> makelsr.py to make output of make check to dissapear, which in turn
> makes all other translators to update their own committishes in
> texidocs.
Fortunately those changes are not cummulative: either one or dozens of
changes to the same string in snippets will appear as one single
change in make check-translation output.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com