Bad objects

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

Bad objects

Francisco Vila
Hello, to be able to produce a translation status report, I need to
fix this ASAP:

warning: ja/notation.tely: fatal: bad object
10fbcf1752dc0bec6ad1101c6948a94529128586
warning: ja/notation/changing-defaults.itely: fatal: bad object
10fbcf1752dc0bec6ad1101c6948a94529128586
warning: ja/notation/cheatsheet.itely: fatal: bad object
d34556def05ad286c0426dcf29118088ed14b153
warning: fr/usage/lilypond-book.itely: fatal: bad object
8e1f0e01b3665bfd8e53ef646ad8fd627d09a41b

I mean, I'd like you to fix these :-)

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


Reply | Threaded
Open this post in threaded view
|

Re: Bad objects

Yoshiki Sawada
I' sure. Please, give me a moment.

I did not know to do "git rev-list HEAD |head -1" for getting the latest committish.
So, I did copy a "commit" from "http://git.savannah.gnu.org/".

Now, I know to get it.
----
Yoshiki Sawada (Japan)


2011/9/16 Francisco Vila <[hidden email]>
Hello, to be able to produce a translation status report, I need to
fix this ASAP:

warning: ja/notation.tely: fatal: bad object
10fbcf1752dc0bec6ad1101c6948a94529128586
warning: ja/notation/changing-defaults.itely: fatal: bad object
10fbcf1752dc0bec6ad1101c6948a94529128586
warning: ja/notation/cheatsheet.itely: fatal: bad object
d34556def05ad286c0426dcf29118088ed14b153
warning: fr/usage/lilypond-book.itely: fatal: bad object
8e1f0e01b3665bfd8e53ef646ad8fd627d09a41b

I mean, I'd like you to fix these :-)

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

Reply | Threaded
Open this post in threaded view
|

Re: Bad objects

Francisco Vila
2011/9/16 Yoshiki Sawada <[hidden email]>:
> I' sure. Please, give me a moment.
>
> I did not know to do "git rev-list HEAD |head -1" for getting the latest

If I copy and paste that in the command line, it works perfectly.

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


Reply | Threaded
Open this post in threaded view
|

Re: Bad objects

Yoshiki Sawada
In reply to this post by Francisco Vila
I got the latest committish from "lilypond/translation", and apply it to bad objects of
the following Japanese translations:
Documentation/ja/notation.tely,
Documentation/ja/notation/changing-defaults.itely, and
Documentation/ja/notation/cheatsheet.itely.

I hope this fix does work well.

And, I want Jean-Charles to fix French translation.
--
Yoshiki Sawada (Japan)


2011/9/16 Francisco Vila <[hidden email]>
Hello, to be able to produce a translation status report, I need to
fix this ASAP:

warning: ja/notation.tely: fatal: bad object
10fbcf1752dc0bec6ad1101c6948a94529128586
warning: ja/notation/changing-defaults.itely: fatal: bad object
10fbcf1752dc0bec6ad1101c6948a94529128586
warning: ja/notation/cheatsheet.itely: fatal: bad object
d34556def05ad286c0426dcf29118088ed14b153
warning: fr/usage/lilypond-book.itely: fatal: bad object
8e1f0e01b3665bfd8e53ef646ad8fd627d09a41b

I mean, I'd like you to fix these :-)

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


0001-Doc-ja-fix-committish-for-Japanese-traslation.patch (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Bad objects

Francisco Vila
2011/9/16 Yoshiki Sawada <[hidden email]>:
> I got the latest committish from "lilypond/translation", and apply it to bad
> objects of

I hope you understand that it means that you are marking the files as
fully updated.

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


Reply | Threaded
Open this post in threaded view
|

Re: Bad objects

Francisco Vila
In reply to this post by Yoshiki Sawada
2011/9/16 Yoshiki Sawada <[hidden email]>:
> I got the latest committish from "lilypond/translation", and apply it to bad
> objects of
> the following Japanese translations:
> Documentation/ja/notation.tely,
> Documentation/ja/notation/changing-defaults.itely, and
> Documentation/ja/notation/cheatsheet.itely.
>
> I hope this fix does work well.

It seems to; pushed.

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


Reply | Threaded
Open this post in threaded view
|

Re: Bad objects

Yoshiki Sawada
Thank you for applying my patch to "lilypond/translation".

I re-checked the titles of the master branch to make sure that
3 documents for which I have updated committish did not changed.
--
Yoshiki Sawada (Japan)

2011/9/17 Francisco Vila <[hidden email]>
2011/9/16 Yoshiki Sawada <[hidden email]>:
> I got the latest committish from "lilypond/translation", and apply it to bad
> objects of
> the following Japanese translations:
> Documentation/ja/notation.tely,
> Documentation/ja/notation/changing-defaults.itely, and
> Documentation/ja/notation/cheatsheet.itely.
>
> I hope this fix does work well.

It seems to; pushed.

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

Reply | Threaded
Open this post in threaded view
|

Re: Bad objects

Francisco Vila
2011/9/16 Yoshiki Sawada <[hidden email]>:
> Thank you for applying my patch to "lilypond/translation".
>
> I re-checked the titles of the master branch to make sure that
> 3 documents for which I have updated committish did not changed.

In the future, if a file gives a 'bad object' message, I think I could
temporarily set its committish to an old tag and push the change so
that it doesn't block the build of translation status.  That would
make the file look very outdated but that would encourage the owner to
update the file and/or the committish more soon than later.

Alternatively I could just warn the owner(s) as I just did, then wait
some hours or days.  I'm fine with either as long as we are not in
rush.  The latter looks more polite, provided that the implied
translators are available, and the former is more practical, and not
harmful in any case.  Opinions?

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


Reply | Threaded
Open this post in threaded view
|

Re: Bad objects

Jean-Charles MALAHIEUDE
Le 16/09/2011 22:51, Francisco Vila disait :

> In the future, if a file gives a 'bad object' message, I think I
> could temporarily set its committish to an old tag and push the
> change so that it doesn't block the build of translation status.
> That would make the file look very outdated but that would encourage
> the owner to update the file and/or the committish more soon than
> later.
>
> Alternatively I could just warn the owner(s) as I just did, then
> wait some hours or days.  I'm fine with either as long as we are not
> in rush.  The latter looks more polite, provided that the implied
> translators are available, and the former is more practical, and not
> harmful in any case.  Opinions?
>

I would propose a mixture of them:

Copy and paste the committish from this translator prior to the "bad"
one, and let him know.

I'm for the moment overbooked because full time job and early delivery
of King Arthur on the CPDL (with too many mistakes i my opinion)...

fr/usage/lilypond-book.itely fixed by
2301f5debf32ac6cb69a62142f4423dc56accf37


Cheers,
Jean-Charles