From: Charles Plessy Date: Sat, 29 Oct 2011 09:47:34 +0000 (+0000) Subject: updated PO files X-Git-Url: https://source.charles.plessy.org/?a=commitdiff_plain;h=fd1f98138f7f2f519f9b21402d29b40892cbd394;p=source.git updated PO files --- diff --git "a/Debian/debi\303\242neries/tout-dans-git.en.po" "b/Debian/debi\303\242neries/tout-dans-git.en.po" index f593a001..54e77fcb 100644 --- "a/Debian/debi\303\242neries/tout-dans-git.en.po" +++ "b/Debian/debi\303\242neries/tout-dans-git.en.po" @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2011-10-29 09:18+0000\n" +"POT-Creation-Date: 2011-10-29 09:47+0000\n" "PO-Revision-Date: 2011-10-29 18:41+0900\n" "Last-Translator: Charles Plessy \n" "Language-Team: Hopla\n" @@ -28,8 +28,9 @@ msgid "[[!meta updated=\"Sat, 29 Oct 2011 17:59:02 +0900\"]]\n" msgstr "[[!meta updated=\"Sat, 29 Oct 2011 17:59:02 +0900\"]]\n" #. type: Plain text -#, no-wrap -msgid "[[!tag Debian brouillon]]\n" +#, fuzzy, no-wrap +#| msgid "[[!tag Debian brouillon]]\n" +msgid "[[!tag Debian]]\n" msgstr "[[!tag Debian brouillon]]\n" #. type: Plain text @@ -45,11 +46,10 @@ msgid "" "de [l'utilisation de Git dans la société Baserock](http://blog.liw.fi/posts/" "future-of-linux-distros/)." msgstr "" -"Saturday started well, reading two stimulating articles on " -"[Planet_Debian](http://planet.debian.org/). One about " -"[GitTogether2011](http://kitenet.net/~joey/blog/entry/GitTogether2011/), and " -"the other about [the use of Git in the Baserock " -"company](http://blog.liw.fi/posts/future-of-linux-distros/)." +"Saturday started well, reading two stimulating articles on [Planet_Debian]" +"(http://planet.debian.org/). One about [GitTogether2011](http://kitenet.net/" +"~joey/blog/entry/GitTogether2011/), and the other about [the use of Git in " +"the Baserock company](http://blog.liw.fi/posts/future-of-linux-distros/)." #. type: Plain text #, no-wrap @@ -68,19 +68,7 @@ msgid "" "que j'ai faite ce matin, pas grand chose à signaler si ce n'est que\n" "-D_FORTIFY_SOURCE=2 n'est plus passé et que par conséquent les\n" "alertes -Wunused-result ont disparu.\n" -msgstr "I like a lot the idea of using Git beyond source code management. This " -"article is itself distributed via a [network of Git " -"repositories](http://www.branchable.com). For the Debian package I develop " -"and that are maintained with Git, I started some time ago to store their " -"build logs in a branch that I called meta. Since " -"[sbuild](http://packages.debian.org/sbuild) [[!debbug 605763 desc=\"filter " -"some variable chains in its logs\"]], the command git diff --word-" -"diff=color became a nice tool to inspect the difference between two " -"package builds. Here is for instance the [update I made this morning for " -"bedtools](http://git.debian.org/?p=debian-med/bedtools.git;a=commitdiff;h=9e" -"1fbef0d98d67999bd334236c75c4bb89d890b7#patch2): we can see that " -"-D_FORTIFY_SOURCE=2 is not passed anymore, and that " -"consequently the -Wunused-result warnings disappeared.\n" +msgstr "I like a lot the idea of using Git beyond source code management. This article is itself distributed via a [network of Git repositories](http://www.branchable.com). For the Debian package I develop and that are maintained with Git, I started some time ago to store their build logs in a branch that I called meta. Since [sbuild](http://packages.debian.org/sbuild) [[!debbug 605763 desc=\"filter some variable chains in its logs\"]], the command git diff --word-diff=color became a nice tool to inspect the difference between two package builds. Here is for instance the [update I made this morning for bedtools](http://git.debian.org/?p=debian-med/bedtools.git;a=commitdiff;h=9e1fbef0d98d67999bd334236c75c4bb89d890b7#patch2): we can see that -D_FORTIFY_SOURCE=2 is not passed anymore, and that consequently the -Wunused-result warnings disappeared.\n" #. type: Plain text msgid "" @@ -93,15 +81,15 @@ msgid "" "réglé lorsque notre archive reconstruira automatiquement les paquet binaires " "téléchargé avec les paquets source, mais pas complètement car il est " "toujours possible de télécharger un paquet binaire isolément." -msgstr "Another advantages of storing build logs is simply to make available " -"information that was not previously: " -"[buildd.debian.org](http://buildd.debian.org) contains the build logs for " -"every architecture except the one used by the package maintainer, often one " -"of the most popular architectures, because the uploads combine source and " -"binary packages. This problem will be solved when our archive will " -"automatically rebuild the binary packages uploaded with the source packages, " -"but it will not be entirely solved as it is still possible to upload binary " -"packages alone.\n" +msgstr "" +"Another advantages of storing build logs is simply to make available " +"information that was not previously: [buildd.debian.org](http://buildd." +"debian.org) contains the build logs for every architecture except the one " +"used by the package maintainer, often one of the most popular architectures, " +"because the uploads combine source and binary packages. This problem will " +"be solved when our archive will automatically rebuild the binary packages " +"uploaded with the source packages, but it will not be entirely solved as it " +"is still possible to upload binary packages alone.\n" #. type: Plain text #, no-wrap @@ -112,11 +100,7 @@ msgid "" "multitude de branches parallèles. Je commence à automatiser la gestion des\n" "journaux, par exemple avec le petit script suivant pour les récupérer depuis\n" "buildd.debian.org.\n" -msgstr "In the meta branch of my Git repositories, the logs are kept " -"side-to-side for every architecture. I am unsure if that the best layout, " -"but for the moment I am uncomfortable with having too many parallel " -"branches. I am starting to automate the work with the logs, for instance " -"with that small script to gather them from buildd.debian.org.\n" +msgstr "In the meta branch of my Git repositories, the logs are kept side-to-side for every architecture. I am unsure if that the best layout, but for the moment I am uncomfortable with having too many parallel branches. I am starting to automate the work with the logs, for instance with that small script to gather them from buildd.debian.org.\n" #. type: Plain text #, no-wrap