Ready to be pushed.

diff --git a/Debian/debiâneries/tout-dans-git.en.po b/Debian/debiâneries/tout-dans-git.en.po
index 54e77fcb11ee60ecfc58841d74f7f9775d0d77f2..d2ab8d994a19559b920cdcdc73b2c4b99026d47f 100644 (file)
--- a/Debian/debiâneries/tout-dans-git.en.po
+++ b/Debian/debiâneries/tout-dans-git.en.po
@@ -1,13 +1,9 @@
-# SOME DESCRIPTIVE TITLE
-# Copyright (C) YEAR Free Software Foundation, Inc.
-# This file is distributed under the same license as the PACKAGE package.
-# Charles Plessy <https://launchpad.net/~plessy>, 2011.
 # Charles Plessy <https://launchpad.net/~plessy>, 2011.
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "POT-Creation-Date: 2011-10-29 09:47+0000\n"
-"PO-Revision-Date: 2011-10-29 18:41+0900\n"
+"PO-Revision-Date: 2011-10-29 18:48+0900\n"
 "Last-Translator: Charles Plessy <https://launchpad.net/~plessy>\n"
 "Language-Team: Hopla\n"
 "Language: en\n"
@@ -31,7 +27,7 @@ msgstr "[[!meta updated=\"Sat, 29 Oct 2011 17:59:02 +0900\"]]\n"
 #, fuzzy, no-wrap
 #| msgid "[[!tag Debian brouillon]]\n"
 msgid "[[!tag Debian]]\n"
-msgstr "[[!tag Debian brouillon]]\n"
+msgstr "[[!tag Debian]]\n"
 
 #. type: Plain text
 #, no-wrap
@@ -68,7 +64,19 @@ msgid ""
 "que j'ai faite ce matin, pas grand chose à signaler si ce n'est que\n"
 "<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=9e1fbef0d98d67999bd334236c75c4bb89d890b7#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.\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=\"can "
+"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=com"
+"mitdiff;h=9e1fbef0d98d67999bd334236c75c4bb89d890b7#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.\n"
 
 #. type: Plain text
 msgid ""