Re: [translations] Re: CG 5.8.3: updating committish of lsr snippets |
[ Thread Index |
Date Index
| More lilynet.net/translations Archives
]
- To: Francisco Vila <paconet.org@xxxxxxxxx>
- Subject: Re: [translations] Re: CG 5.8.3: updating committish of lsr snippets
- From: Federico Bruni <fedelogy@xxxxxxxxx>
- Date: Sun, 23 Oct 2011 20:58:53 +0200
- Cc: Lily-Devel List <lilypond-devel@xxxxxxx>, 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; bh=zHU42NhURQSyYEPKKU4r6hGyBhlSuUj9MMYH6OodpYk=; b=nrtG8k2zOsGXsxbtb+kaiDBWS9NZgTa063hvFy1tS1ylQmtkBkluW4dDrKF48Pv2AI ZbN4kra6nLTn/aW1tlRl4jti7klDzKk8h1iMCewaaKfO151QBW4KCz9HbPhPruFLdQEM kqt/td+YSdbC59yeh8G2rQR6aacvQC7phUbqs=
This is a multi-part message in MIME format.
I've almost gave up here.
I don't have skills nor time to spend on this issue, sorry.
The attached patch fixes the bad object error.
I have no idea if it's correct and how the updating of .texidoc files works.
make check-translation still looks weird to me, but I won't care for now....
What I've done
=========
Which is the committish that I should have used in my .texidoc files
when I committed them?
The answer should be: the commit id (my commit) of the makelsr that
processed them. Right?
So, I checked the log of each file in Documentation/snippets.
I noticed that most of them had this committish (c3b51...), so I
substitued the bad object:
sed -i
's/514674cb00c18629242dfcde0c1a4976758adc56/c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c/g'
*.texidoc
Then I fixed the few files that are related to a different committish.
This is the final committish situation in Documentation/it/texidocs:
$ cat * | grep committish
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: 34607d3e36a93030690ccd780a7ffce621ca1e0f
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: 34607d3e36a93030690ccd780a7ffce621ca1e0f
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: c3b519f0dd5ff0f8ccfc9a39ed1fe8df8b43741c
%% Translation of GIT committish: 34607d3e36a93030690ccd780a7ffce621ca1e0f