| [translations] Re: CG 5.8.3: updating committish of lsr snippets |
[ Thread Index |
Date Index
| More lilynet.net/translations Archives
]
- To: Lily-Devel List <lilypond-devel@xxxxxxx>
- Subject: [translations] Re: CG 5.8.3: updating committish of lsr snippets
- From: Federico Bruni <fedelogy@xxxxxxxxx>
- Date: Sun, 09 Oct 2011 17:27:27 +0200
- Cc: LilyPond Translation <translations@xxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=mlP9OJXtjb00XigX91oZ5RWV52yA7wVRGtbEygQu5QE=; b=FD95gO9DIG2IypBvGip9/hKW63pO4OyFEREu225Xhr9LUBTThO26xCT4Cin5IQEXaU b/WYD3oB5I5Ghp7Mw3GobKCyzhYusJwwHT+PEEJI7koPVnkTT6s18As3ME5jeCFao754 ke0N8n6+m3ksDNGgog2Rb8B7L8E0RFs4Sq3pM=
Il 02/10/2011 12:10, Federico Bruni ha scritto:
Two months ago I discussed with Francisco a problem with committish
and LSR snippets:
http://lilypond-translations.3384276.n2.nabble.com/Doc-it-revision-of-snippets-in-LM-please-backport-to-2-14-td6600646.html
(read last messages in particular)
Information in CG 5.8.3, Updating translation committishes, is Ok for
people who have push access.
For those who haven't, a different method should be recommended.
Otherwise the maintenance scripts will complain about bad objects (non
existing committishes).
In the thread above Francisco proposed a solution.
Please think about what's the best solution and update CG.
Thanks,
Federico
Ok, nobody is interested in this issue.
Could you please tell me which committish should I use to avoid the bad
object warning? Also, if I don't fix the committish, I won't be able to
update the translation in the future...
I've tried:
cd Documentation/it/texidocs
sed -i
's/514674cb00c18629242dfcde0c1a4976758adc56/34607d3e36a93030690ccd780a7ffce621ca1e0f/g'
*.texidoc
But it doesn't seem to be the right committish.
Please help me, I know nothing about Git.