Premier essai de traduction.

diff --git a/Debian/debiâneries/tout-dans-git.en.po b/Debian/debiâneries/tout-dans-git.en.po
index 2ff6670839ba25aca49ca73d08e8cadd846a2905..a3ea274289b59a9de7cc5cec7241b81eba02c413 100644 (file)
--- a/Debian/debiâneries/tout-dans-git.en.po
+++ b/Debian/debiâneries/tout-dans-git.en.po
@@ -1,40 +1,40 @@
 # SOME DESCRIPTIVE TITLE
 # Copyright (C) YEAR Free Software Foundation, Inc.
 # This file is distributed under the same license as the PACKAGE package.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+# Charles Plessy <https://launchpad.net/~plessy>, 2011.
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "POT-Creation-Date: 2011-10-29 09:18+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <LL@li.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2011-10-29 18:39+0900\n"
+"Last-Translator: Charles Plessy <https://launchpad.net/~plessy>\n"
+"Language-Team: Hopla\n"
+"Language: en\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Generator: Virtaal 0.7.0\n"
 
 #. type: Plain text
 #, no-wrap
 msgid "[[!meta date=\"Sat, 29 Oct 2011 17:59:02 +0900\"]]\n"
-msgstr ""
+msgstr "[[!meta date=\"Sat, 29 Oct 2011 17:59:02 +0900\"]]\n"
 
 #. type: Plain text
 #, no-wrap
 msgid "[[!meta updated=\"Sat, 29 Oct 2011 17:59:02 +0900\"]]\n"
-msgstr ""
+msgstr "[[!meta updated=\"Sat, 29 Oct 2011 17:59:02 +0900\"]]\n"
 
 #. type: Plain text
 #, no-wrap
 msgid "[[!tag Debian brouillon]]\n"
-msgstr ""
+msgstr "[[!tag Debian brouillon]]\n"
 
 #. type: Plain text
 #, no-wrap
 msgid "[[!meta title=\"Tout dans Git\"]]\n"
-msgstr ""
+msgstr "[[! meta title = \"Everything in Git\"]]\n"
 
 #. type: Plain text
 msgid ""
@@ -44,6 +44,11 @@ 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/)."
 
 #. type: Plain text
 #, no-wrap
@@ -63,6 +68,19 @@ msgid ""
 "<code>-D_FORTIFY_SOURCE=2</code> n'est plus passé et que par conséquent les\n"
 "alertes <code>-Wunused-result</code> 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 <code>meta</code>.  Since "
+"[sbuild](http://packages.debian.org/sbuild) [[!debbug 605763 desc=\"filter "
+"some variable chains in its logs\"]], the command <code>git diff --word-"
+"diff=color</code> 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 "
+"<code>-D_FORTIFY_SOURCE=2</code> is not passed anymore, and that "
+"consequently the <code>-Wunused-result</code> warnings disappeared."
 
 #. type: Plain text
 msgid ""
@@ -76,6 +94,15 @@ msgid ""
 "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. "
 
 #. type: Plain text
 #, no-wrap
@@ -87,24 +114,32 @@ msgid ""
 "journaux, par exemple avec le petit script suivant pour les récupérer depuis\n"
 "buildd.debian.org.\n"
 msgstr ""
+"In the <code>meta</code> 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."
 
 #. type: Plain text
 #, no-wrap
 msgid "<pre>\n"
-msgstr ""
+msgstr "<pre>\n"
 
 #. type: Plain text
 #, no-wrap
 msgid "#!/bin/bash\n"
-msgstr ""
+msgstr "#!/bin/bash\n"
 
 #. type: Plain text
 msgid "BASEURL=buildd.debian.org:/srv/buildd.debian.org/db PACKAGE=$1 shift"
 msgstr ""
+"BASEURL=buildd.debian.org:/srv/buildd.debian.org/db\n"
+"PACKAGE=$1\n"
+"shift\n"
 
 #. type: Plain text
 msgid "for version in \"$*\""
-msgstr ""
+msgstr "for version in \"$*\"\n"
 
 #. type: Plain text
 #, no-wrap
@@ -117,6 +152,13 @@ msgid ""
 "  done\n"
 "done\n"
 msgstr ""
+"do\n"
+"  scp $BASEURL/${PACKAGE:0:1}/$PACKAGE/${version}/* .\n"
+"  for arch in $(ls *bz2 | sed 's/_.*//g')\n"
+"    do bzcat ${arch}*bz2 > ${arch}.log\n"
+"    rm ${arch}_*_log.bz2;\n"
+"  done\n"
+"done\n"
 
 #. type: Plain text
 #, no-wrap
@@ -124,3 +166,5 @@ msgid ""
 "exit\n"
 "</pre>\n"
 msgstr ""
+"exit\n"
+"</pre>\n"