Changeset 189 in tracdarcs for README.rst

Timestamp:

06/11/10 16:55:39 (3 years ago)

Author:

lele@…

Hash name:

20100611145539-97f81-3fbf064055a682248b642255691cdfca2fec1617

Message:

Cosmetic and little fixes to the documentation

File:

• README.rst (modified) (3 diffs)

README.rst

@@ -9 +9 @@
 __ http://trac.edgewall.org/wiki/MultipleRepositorySupport
 __ http://trac.edgewall.org/milestone/0.12
-__ http://trac.edgewall.org/browser/sandbox/multirepos
 
 It used to work on 0.11, and even with 0.10, at least up to version
@@ -71 +70 @@
 -----------------------
 
-The recommended way to trigger the sync between the repository and the
-Trac instance is by using a darcs `post hook`__ on its ``apply``: in
-this way the database will be updated as soon as darcs finish applying
-any new changeset.
+The `recommended way`__ to trigger the sync between the repository and
+the Trac instance is by using a darcs `post hook`__ on its ``apply``:
+in this way the database will be updated as soon as darcs finish
+applying any new changeset.
 
 This can be accomplished by putting something like the following
 setting into the repository ``_darcs/prefs/defaults`` file::
 
-  apply posthook trac-admin TRAC_ENV changeset add $(pwd) $(python -m tracdarcs.changesparser)
+  apply posthook trac-admin TRAC_ENV changeset added $(pwd) $(python -m tracdarcs.changesparser)
   apply run-posthook
 
@@ -85 +84 @@
 the related trac instance.
 
-Btw, ``python -m tracdarcs.changesparser`` is just a quick way of
-extracting the list of changeset hashes from the the ``darcs changes
---xml`` format: it accepts the input either as the
-``$DARCS_PATCHES_XML`` or from standard input::
-
-  $ darcs changes --xml | python -m tracdarcs.changesparser | head -3
-  20100611081300-97f81-bc5c1f7acf0c168bbfa9fb911e3cc2a4e71d5eef
-  20100610150339-97f81-cd1b73f2ba1b1d98c28542ecbd1d5e2bd9052056
-  20100512164420-97f81-de3fbc73d7c401fb92503ef1b25e19e0f48d2ad1
-
-
+.. note:: ``python -m tracdarcs.changesparser`` is just a quick way of
+   extracting the list of changeset hashes from the the ``darcs
+   changes --xml`` format: it accepts the input either as the
+   ``$DARCS_PATCHES_XML`` or from standard input::
+
+    $ darcs changes --xml | python -m tracdarcs.changesparser | head -3
+    20100611081300-97f81-bc5c1f7acf0c168bbfa9fb911e3cc2a4e71d5eef
+    20100610150339-97f81-cd1b73f2ba1b1d98c28542ecbd1d5e2bd9052056
+    20100512164420-97f81-de3fbc73d7c401fb92503ef1b25e19e0f48d2ad1
+
+At that point, you could deactivate the per request sync that Trac
+still does by default, by setting ``repository_sync_per_request`` to
+an empty value in the ``[trac]`` section of the configuration.
+
+__ http://trac.edgewall.org/wiki/0.12/TracRepositoryAdmin#ExplicitSync
 __ http://darcs.net/manual/node7.html#SECTION00712000000000000000