[svnbook] r6054 committed - branches/1.8/fr/book

[chris-nanteuil at users.sourceforge.net]

Revision: 6054
          http://sourceforge.net/p/svnbook/source/6054
Author:   chris-nanteuil
Date:     2022-03-12 15:41:02 +0000 (Sat, 12 Mar 2022)
Log Message:
-----------
Keeping French branch in sync with English version.
Thanks Daniel Shahaf for the additional precision.

Modified Paths:
--------------
    branches/1.8/fr/book/ch03-advanced-topics.xml

Property Changed:
----------------
    branches/1.8/fr/book/
    branches/1.8/fr/book/ch03-advanced-topics.xml

Index: branches/1.8/fr/book
===================================================================
--- branches/1.8/fr/book	2022-03-12 10:02:09 UTC (rev 6053)
+++ branches/1.8/fr/book	2022-03-12 15:41:02 UTC (rev 6054)

Property changes on: branches/1.8/fr/book
___________________________________________________________________
Added: svn:mergeinfo
## -0,0 +1 ##
+/trunk/en/book:5065-6053
\ 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	2022-03-12 10:02:09 UTC (rev 6053)
+++ branches/1.8/fr/book/ch03-advanced-topics.xml	2022-03-12 15:41:02 UTC (rev 6054)
@@ -7639,6 +7639,7 @@
         whose unwanted persistence after an error can cause a repository
         to be <quote>wedged,</quote> as described in
         <xref linkend="svn.berkeleydb.maintenance.recovery" />.</para>
+
 -->
       <para>
         <indexterm>
@@ -7654,6 +7655,79 @@
         indiqué dans <xref linkend="svn.berkeleydb.maintenance.recovery"
         />.</para>
 <!--
+      <para>
+        <indexterm>
+          <primary>locks</primary>
+          <secondary>svnsync</secondary>
+        </indexterm>Additionally, there are <firstterm>svnsync
+        locks</firstterm>, which effect mutual exclusion between multiple
+        instances of the <command>svnsync</command> command that write
+        to the same mirror of a repository.  This is the sort of lock
+        implemented by the <literal>svn:sync-lock</literal> revision
+        property, as described in <xref
+        linkend="svn.reposadmin.maint.replication.svnsync" />.</para>
+-->
+      <para>
+        <indexterm>
+          <primary>verrous</primary>
+          <secondary>svnsync</secondary>
+        </indexterm>Il existe aussi les <firstterm>verrous
+        svnsync</firstterm>, qui assurent l'exclusion mutuelle entre
+        plusieurs instances de la commande <command>svnsync</command>
+        quand elles écrivent dans le même miroir d'un dépôt. La propriété
+        de révision <literal>svn:sync-lock</literal> utilise ce type de
+        verrou, comme décrit dans <xref
+        linkend="svn.reposadmin.maint.replication.svnsync" />.</para>
+
+<!--
+      <para>
+        <indexterm>
+          <primary>locks</primary>
+          <secondary>svnrdump</secondary>
+        </indexterm>Next, there are <firstterm>svnrdump
+        locks</firstterm>.  These are very much like svnsync locks, but
+        are associated with the <command>svnrdump load</command> command
+        (described in <xref linkend="svn.reposadmin.maint.migrate.svnrdump"
+        />) instead of <command>svnsync</command>.</para>
+-->
+
+      <para>
+        <indexterm>
+          <primary>locks</primary>
+          <secondary>svnrdump</secondary>
+        </indexterm>Encore un type de verrou, les <firstterm>verrous
+        svnrdump</firstterm>. Ils ressemblent beaucoup aux verrous svnsync,
+        mais sont associés aux commandes <command>svnrdump load</command>
+        (décrites dans <xref linkend="svn.reposadmin.maint.migrate.svnrdump"
+        />).</para>
+
+<!--
+      <para>
+        <indexterm>
+          <primary>locks</primary>
+          <secondary>SQLite</secondary>
+        </indexterm>Finally, there are <firstterm>SQLite
+        locks</firstterm>.  These are used by the SQLite library (<ulink
+        url="https://www.sqlite.org/" />) to serialize access to SQLite
+        databases used by Subversion under the hood.  See, for example,
+        the <literal>exclusive-locking</literal> option in <xref
+        linkend="svn.advanced.confarea.opts.config" />.</para>
+-->
+
+      <!-- No need to mention svn_mutex__t at this time. -->
+
+      <para>
+        <indexterm>
+          <primary>locks</primary>
+          <secondary>SQLite</secondary>
+        </indexterm>Enfin, abordons les <firstterm>verrous
+        SQLite</firstterm>. Ils sont utilisés par la bibliothèque SQLite
+        (<ulink url="https://www.sqlite.org/" />) pour sérialiser les accès
+        aux bases de données SQLite que Subversion utilise en interne.
+        Regardez, par exemple, l'option <literal>exclusive-locking</literal>
+        dans <xref linkend="svn.advanced.confarea.opts.config" />.</para>
+
+<!--
       <para>You can generally forget about these other kinds of locks
         until something goes wrong that requires you to care about
         them.  In this book, <quote>lock</quote> means the first sort
@@ -7673,6 +7747,7 @@
     <sect2 id="svn.advanced.locking.creation">
 <!--
       <title>Creating Locks</title>
+
 -->
       <title>Création d'un verrou</title>
 


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-5965
+/trunk/en/book/ch03-advanced-topics.xml:5065-6053
 /trunk/src/fr/book/ch03-advanced-topics.xml:3306-3976
\ No newline at end of property