| 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:22:41 +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=xaC0JR3v5/2H3rMjZUh/LXC7CRdecMwovderp+yAa2k=; b=vpWtbgffiRzHpj11dnK0bTP/qHcopzxud3Fv6lLWCQ7QPC7/yQoeVgE2cWnmV7MpSZ XTPnYl9cCynTNL3zA03UmWUIEvMxh414SKQ06AhNNwrfW31pm/riRGVJ2W1tJt6Nuk7+ 0QaJy0GIgdjif+GciXKtPF6s1K+w0aWhSRjSY=
2012/1/30 Federico Bruni <fedelogy@xxxxxxxxx>:
> I've pulled and I think it's ok.
> I've checked the logs of snippets: the last update was in November, so no
> edit is missing.
But your output of make check-translation still will contain the last
change: "COMMITTISH" to real committish in snippets/.ly due to my last
run of makelsr.py
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.
Whe should live with outdated committishes in texidocs and run makelsr
only if there are real changes in snippets that make texidocs worth of
updating.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com