From kde-i18n-doc Sun Nov 23 16:21:44 2014 From: Chusslove Illich Date: Sun, 23 Nov 2014 16:21:44 +0000 To: kde-i18n-doc Subject: Re: Some Calligra catalog files renamed today, master-only Message-Id: <201411231721.47874.caslav.ilic () gmx ! net> X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=141675973818813 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart2227335.9a7Igjisnj" --nextPart2227335.9a7Igjisnj Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable > [: Luigi Toscano :] > Thank you for the instructions! I tried to do it (r1407104), please check > if something is missing so that in case next time I can do it correctly. Yes, everything is as expected. I forgot to add that you can test if things went well (in technical sense) by executing summit gather on templates afterwards: posummit scripts/messages.summit templates gather If it starts processing, then every branch catalog is covered by some existing summit catalog, and vice versa. Otherwise, it will inform about all detected mismatches and stop. Of course, it could also stop on an unrelated mismatch (e.g. this morning a new appdata catalog appeared in one branch), which should be clear from the output. On a side note, some mismatches could also be by intention, since posummit may have a default way of resolving them. Reruning with --force option will make it do so, and then all resolvable mismatches will not be reported (e.g. in absence of any related mapping, a new summit catalog would be automatically created for a new branch catalog). =2D-=20 Chusslove Illich (=D0=A7=D0=B0=D1=81=D0=BB=D0=B0=D0=B2 =D0=98=D0=BB=D0=B8= =D1=9B) --nextPart2227335.9a7Igjisnj Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEABECAAYFAlRyCZsACgkQMSGXgigGr3FgSQCeMT62KmZ32BLoLM4N/iNfjQCu HJsAn1/LIJ3aTzSGz84wW//IqkCh4+B9 =BDHZ -----END PGP SIGNATURE----- --nextPart2227335.9a7Igjisnj--