[svnbook] r5577 committed - branches/1.8/fr/book
chris-nanteuil at users.sourceforge.net
chris-nanteuil at users.sourceforge.net
Tue Jan 9 16:30:24 CST 2018
Revision: 5577
http://sourceforge.net/p/svnbook/source/5577
Author: chris-nanteuil
Date: 2018-01-09 22:30:23 +0000 (Tue, 09 Jan 2018)
Log Message:
-----------
[fr] Following English version.
Modified Paths:
--------------
branches/1.8/fr/book/ch03-advanced-topics.xml
branches/1.8/fr/book/ch04-branching-and-merging.xml
branches/1.8/fr/book/ch05-repository-admin.xml
branches/1.8/fr/book/ch06-server-configuration.xml
Property Changed:
----------------
branches/1.8/fr/book/
branches/1.8/fr/book/ch03-advanced-topics.xml
branches/1.8/fr/book/ch04-branching-and-merging.xml
branches/1.8/fr/book/ch05-repository-admin.xml
branches/1.8/fr/book/ch06-server-configuration.xml
Index: branches/1.8/fr/book
===================================================================
--- branches/1.8/fr/book 2018-01-09 20:38:30 UTC (rev 5576)
+++ branches/1.8/fr/book 2018-01-09 22:30:23 UTC (rev 5577)
Property changes on: branches/1.8/fr/book
___________________________________________________________________
Modified: svn:mergeinfo
## -1 +1 ##
-/trunk/en/book:5065-5557
\ No newline at end of property
+/trunk/en/book:5065-5576
\ No newline at end of property
Modified: branches/1.8/fr/book/ch03-advanced-topics.xml
===================================================================
--- branches/1.8/fr/book/ch03-advanced-topics.xml 2018-01-09 20:38:30 UTC (rev 5576)
+++ branches/1.8/fr/book/ch03-advanced-topics.xml 2018-01-09 22:30:23 UTC (rev 5577)
@@ -8631,14 +8631,13 @@
<para>Subversion defaults to the <quote>softer</quote>
approach, but still allows administrators to create stricter
enforcement policies through the use of hook scripts. In
- particular, the <filename>pre-lock</filename> and
- <filename>pre-unlock</filename> hooks allow administrators
+ particular, the pre-lock and
+ pre-unlock hooks allow administrators
to decide when lock creation and lock releases are allowed
to happen. Depending on whether a lock already exists,
these two hooks can decide whether to allow a certain user
to break or steal a lock. The
- <filename>post-lock</filename> and
- <filename>post-unlock</filename> hooks are also available,
+ post-lock and post-unlock hooks are also available,
and can be used to send email after locking actions. To
learn more about repository hooks, see
<xref linkend="svn.reposadmin.hooks" />.</para>
@@ -8647,8 +8646,8 @@
mais autorise cependant les administrateurs à mettre en place
une politique plus stricte via l'utilisation de procédures
automatiques. En particulier, les procédures automatiques de
- pré-verrouillage (fichier <filename>pre-lock</filename>) et de
- pré-déverrouillage (fichier <filename>pre-unlock</filename>)
+ pré-verrouillage (<literal>pre-lock</literal>) et de
+ pré-déverrouillage (<literal>pre-unlock</literal>)
permettent aux administrateurs de décider dans quelles
situations la création ou la libération d'un verrou est
autorisée. En fonction de l'existence préalable ou non d'un
Property changes on: branches/1.8/fr/book/ch03-advanced-topics.xml
___________________________________________________________________
Modified: svn:mergeinfo
## -1,3 +1,3 ##
/branches/1.5/fr/book/ch03-advanced-topics.xml:3977-5223
-/trunk/en/book/ch03-advanced-topics.xml:5065-5557
+/trunk/en/book/ch03-advanced-topics.xml:5065-5576
/trunk/src/fr/book/ch03-advanced-topics.xml:3306-3976
\ No newline at end of property
Modified: branches/1.8/fr/book/ch04-branching-and-merging.xml
===================================================================
--- branches/1.8/fr/book/ch04-branching-and-merging.xml 2018-01-09 20:38:30 UTC (rev 5576)
+++ branches/1.8/fr/book/ch04-branching-and-merging.xml 2018-01-09 22:30:23 UTC (rev 5577)
@@ -6245,7 +6245,7 @@
repository to prevent older clients from committing changes.
The easy way to do this is by inspecting
the <quote>capabilities</quote> parameter in
- the <literal>start-commit</literal> hook script. If the
+ the start-commit hook script. If the
client reports itself as having <literal>mergeinfo</literal>
capabilities, the hook script can allow the commit to start.
If the client doesn't report that capability, have the hook
@@ -6258,7 +6258,8 @@
configurer votre dépôt pour qu'il empêche les anciens clients
de propager des modifications. La méthode la plus simple est
d'examiner le paramètre <quote>capabilities</quote> dans la
- procédure automatique de début de propagation. Si le client
+ procédure automatique de début de propagation
+ (<literal>start-commit</literal>). Si le client
indique être capable de gérer les <literal>mergeinfo</literal>,
la procédure automatique peut l'autoriser à commencer la
propagation. Si le client n'indique pas en être capable, la
Property changes on: branches/1.8/fr/book/ch04-branching-and-merging.xml
___________________________________________________________________
Modified: svn:mergeinfo
## -1,2 +1,2 ##
-/trunk/en/book/ch04-branching-and-merging.xml:5065-5557
+/trunk/en/book/ch04-branching-and-merging.xml:5065-5576
/trunk/src/fr/book/ch04-branching-and-merging.xml:3306-3976
\ No newline at end of property
Modified: branches/1.8/fr/book/ch05-repository-admin.xml
===================================================================
--- branches/1.8/fr/book/ch05-repository-admin.xml 2018-01-09 20:38:30 UTC (rev 5576)
+++ branches/1.8/fr/book/ch05-repository-admin.xml 2018-01-09 22:30:23 UTC (rev 5577)
@@ -1388,7 +1388,7 @@
<para>The syntax of the <filename>hooks-env</filename> file is
pretty straightforward: each section name is the name of a
hook script (such as <literal>pre-commit</literal>
- or <literal>post-revprop-change</literal>, and the
+ or <literal>post-revprop-change</literal>), and the
configuration items inside that section are treated as
mappings of environment variable names to desired values.
Additionally, there is a
@@ -1881,7 +1881,7 @@
about a commit transaction should be considered read-only.
Instead of modifying a transaction to polish its payload,
simply <emphasis>validate</emphasis> the transaction in
- the <filename>pre-commit</filename> hook and reject the
+ the pre-commit hook and reject the
commit if it does not meet the desired requirements. As a
bonus, your users will learn the value of careful,
compliance-minded work habits.</para>
@@ -2082,8 +2082,8 @@
attempts to change the repository. <command>svnlook</command>
is typically used by the repository hooks for reporting the
changes that are about to be committed (in the case of the
- <command>pre-commit</command> hook) or that were just
- committed (in the case of the <command>post-commit</command>
+ pre-commit hook) or that were just
+ committed (in the case of the post-commit
hook) to the repository. A repository administrator may use
this tool for diagnostic purposes.</para>
-->
@@ -2109,9 +2109,9 @@
est généralement utilisé par les procédures automatiques du
dépôt pour signaler les changements qui vont être propagés
(dans le cas de la procédure automatique
- <command>pre-commit</command>) ou qui viennent d'être propagés
+ <literal>pre-commit</literal>) ou qui viennent d'être propagés
(dans le cas de la procédure automatique
- <command>post-commit</command>). Un administrateur peut être
+ <literal>post-commit</literal>). Un administrateur peut être
amené à utiliser cet outil à des fins de diagnostic.</para>
<!--
@@ -2651,7 +2651,7 @@
<para>Sometimes a user will have an error in her log message (a
misspelling or some misinformation, perhaps). If the
repository is configured (using the
- <literal>pre-revprop-change</literal> hook; see
+ pre-revprop-change hook; see
<xref linkend="svn.reposadmin.hooks" />) to accept changes to
this log message after the commit is finished, the user
can <quote>fix</quote> her log message remotely using
@@ -2705,8 +2705,8 @@
<para>The <command>svnadmin setlog</command> command, by
default, is still bound by the same protections against
modifying unversioned properties as a remote client
- is—the <literal>pre-revprop-change</literal> and
- <literal>post-revprop-change</literal> hooks are still
+ is—the pre-revprop-change and
+ post-revprop-change hooks are still
triggered, and therefore must be set up to accept changes of
this nature. But an administrator can get around these
protections by passing the <option>- -bypass-hooks</option>
@@ -2715,7 +2715,7 @@
<para>La commande <command>svnadmin setlog</command>, par défaut,
possède les mêmes garde-fous pour empêcher de modifier des
propriétés non suivies en versions qu'un client distant (les
- procédures automatiques <literal>pre-</literal> et
+ procédures automatiques <literal>pre-revprop-change</literal> et
<literal>post-revprop-change</literal> sont toujours activées et
doivent donc être configurées afin d'accepter ce type de
changement. Mais un administrateur peut contourner ces
@@ -3849,7 +3849,7 @@
<para>Another neat trick you can perform with this
<option>- -incremental</option> option involves appending to an
existing dump file a new range of dumped revisions. For
- example, you might have a <literal>post-commit</literal> hook
+ example, you might have a post-commit hook
that simply appends the repository dump of the single revision
that triggered the hook. Or you might have a script that runs
nightly to append dump file data for all the revisions that
@@ -4960,7 +4960,7 @@
that only it is doing those things. We accomplish this by
implementing two of the repository event
hooks—pre-revprop-change and start-commit. Our
- <filename>pre-revprop-change</filename> hook script is found
+ pre-revprop-change hook script is found
in <xref
linkend="svn.reposadmin.maint.replication.pre-revprop-change"
/>, and basically verifies that the user attempting the
@@ -5017,7 +5017,7 @@
<para>That covers revision property changes. Now we need to
ensure that only the <literal>syncuser</literal> user is
permitted to commit new revisions to the repository. We do
- this using a <filename>start-commit</filename> hook script
+ this using a start-commit hook script
such as the one in <xref
linkend="svn.reposadmin.maint.replication.start-commit"
/>.</para>
Property changes on: branches/1.8/fr/book/ch05-repository-admin.xml
___________________________________________________________________
Modified: svn:mergeinfo
## -1,3 +1,3 ##
/branches/1.5/fr/book/ch05-repository-admin.xml:3977-5144
-/trunk/en/book/ch05-repository-admin.xml:5065-5557
+/trunk/en/book/ch05-repository-admin.xml:5065-5576
/trunk/src/fr/book/ch05-repository-admin.xml:3306-3976
\ No newline at end of property
Modified: branches/1.8/fr/book/ch06-server-configuration.xml
===================================================================
--- branches/1.8/fr/book/ch06-server-configuration.xml 2018-01-09 20:38:30 UTC (rev 5576)
+++ branches/1.8/fr/book/ch06-server-configuration.xml 2018-01-09 22:30:23 UTC (rev 5577)
@@ -3657,29 +3657,6 @@
the <filename>svnserve.conf</filename>.</para>
<!--
- <para>You may also specify the location of a groups file
- which is versioned inside a Subversion repository.
- Use a local URL (one which begins
- with <literal>file://</literal>) to refer to an
- absolute Subversion-versioned file. Alternatively,
- you may use a repository relative URL (one which
- begins with <literal>^/</literal>) to cause
- <command>svnserve</command> to consult for each
- repository the group file stored at the specified
- relative URL within that repository.</para>
--->
- <para>You may also specify the location of a groups file
- which is versioned inside a Subversion repository.
- Use a local URL (one which begins
- with <literal>file://</literal>) to refer to an
- absolute Subversion-versioned file. Alternatively,
- you may use a repository relative URL (one which
- begins with <literal>^/</literal>) to cause
- <command>svnserve</command> to consult for each
- repository the group file stored at the specified
- relative URL within that repository.</para>
-
-<!--
<para>See
<xref linkend="svn.reposadmin.hooks.configuration" />
for detailed information regarding the hook script
@@ -4467,7 +4444,7 @@
<!--
<para>Of course, you might have already set up
- a <filename>pre-commit</filename> hook script to prevent
+ a pre-commit hook script to prevent
commits (see <xref linkend="svn.reposadmin.hooks"/>).
But as you read on, you'll see that it's also possible to use
Apache's built-in methods to restrict access in specific
@@ -4474,7 +4451,7 @@
ways.</para>
-->
<para>Bien sûr, vous avez peut-être déjà mis en place une
- procédure automatique <filename>pre-commit</filename> pour
+ procédure automatique <literal>pre-commit</literal> pour
empêcher les propagations (voir <xref
linkend="svn.reposadmin.hooks"/>). Mais en progressant
dans la lecture de ce chapitre, vous verrez qu'il est également
@@ -7494,7 +7471,7 @@
<!--
<para>First, make sure that each slave repository has a
- <filename>pre-revprop-change</filename> hook script which
+ pre-revprop-change hook script which
allows remote revision property changes. (This is
standard procedure for being on the receiving end of
<command>svnsync</command>.) Then log into the master
@@ -7504,7 +7481,7 @@
-->
<para>Tout d'abord, assurez-vous que chaque dépôt esclave
possède une procédure automatique
- <filename>pre-revprop-change</filename> qui autorise les
+ <literal>pre-revprop-change</literal> qui autorise les
modifications de propriétés de révisions à distance (cette
étape fait partie de la procédure standard pour un serveur
qui reçoit les révisions de <command>svnsync</command>).
@@ -7607,7 +7584,7 @@
<!--
<para>After this is done, we configure the master server's
- <literal>post-commit</literal> hook script to invoke
+ post-commit hook script to invoke
<command>svnsync</command> on each slave server:</para>
-->
<para>Une fois ceci fait, nous configurons la procédure
@@ -7650,8 +7627,8 @@
commands to run in the background so that the Subversion
client isn't left waiting forever for the commit to
finish. In addition to this
- <literal>post-commit</literal> hook, you'll need a
- <literal>post-revprop-change</literal> hook as well so
+ post-commit hook, you'll need a
+ post-revprop-change hook as well so
that when a user, say, modifies a log message, the slave
servers get that change also:</para>
-->
Property changes on: branches/1.8/fr/book/ch06-server-configuration.xml
___________________________________________________________________
Modified: svn:mergeinfo
## -1,3 +1,3 ##
/branches/1.5/fr/book/ch06-server-configuration.xml:3977-5196
-/trunk/en/book/ch06-server-configuration.xml:5065-5557
+/trunk/en/book/ch06-server-configuration.xml:5065-5576
/trunk/src/fr/book/ch06-server-configuration.xml:3306-3976
\ No newline at end of property
More information about the svnbook-dev
mailing list