Changes between Version 4 and Version 5 of DarcsBackend

Timestamp:

06/21/08 15:17:18 (5 years ago)

Author:

lele

Comment:

Explain how to reference a changeset by its hashname

DarcsBackend

@@ -53 +53 @@
 So, for the purpose of tracking it, with the assumption above, the backend just consider the enumeration of the patches that comes out from {{{darcs changes --reverse}}} is ''stable'', and thus the ''first'' patch will called [1], the second [2], and so on, without exceeding in fantasy ;-)
 
-However, I don't exclude to hack in a more darcsish way to point to the patches, most probably by using reStructuredText interpreted roles..., sooner or later.
+However, as of version 0.7 the backend properly recognizes also the ''hashname'' of the patches: this allows you to refer to any particular changeset either by its ''local cardinal numer'' '''or''' by its ''universal unique id''. So, for example, the patch that introduced this functionality may be reached:
+
+ * by its number, [120]
+ * by its hash, [20080617165959-97f81-01b798f29e7c925e146c0876e73dc6879e4d9156]: here I actually wrote `[20080617165959-97f81-01b798f29e7c925e146c0876e73dc6879e4d9156]`, and Trac replaced that with its ''local'' cardinal number to avoid useless verbosity
+ * using the URL, changeset:20080617165959-97f81-01b798f29e7c925e146c0876e73dc6879e4d9156
 
 == Cache ==
 
-To work reasonably fast, the backend automatically and incrementally builds a cache of all the needed versions of any file in the repository. It does '''not''' keep a copy of the whole repository, only the files effectively changed by any given changeset. It uses a subdirectory of the `_darcs` metadir of the repository,  `trac_cache`, that in turn will contains a directory named after the ''revision'' of the changeset. It can be erased at any time, the backed will recreate it and start rebuilding the version at the following request.
+To work reasonably fast, the backend automatically and incrementally builds a cache of all the needed versions of any file in the repository. It does '''not''' keep a copy of the whole repository, only the files effectively changed by any given changeset. ~~It uses a subdirectory of the `_darcs` metadir of the repository,  `trac_cache`, that in turn will contains a directory named after the ''revision'' of the changeset. It can be erased at any time, the backed will recreate it and start rebuilding the version at the following request. The cache directory '''must''' have write permission for the user executing the trac process, usually ''www-data''.~~
 
-The cache directory '''must''' have write permission for the user executing the trac process, usually ''www-data''.
+The cache is now kept in a table of the database: doing a ''resync'' will erase it.
+
 == Configuration ==
 
-Changesets [1862] and [1863] introduced a `darcs` configuration section in the TracIni file. It allows the customization of the actual external command to execute (`command`), the location of the cache directory (`cachedir`) to use instead of keeping it under repository's `_darcs` metadir. Another option is `dont_escape_8bit`, that basically adds `DARCS_DONT_ESCAPE_8BIT=1` as prefix to the command: other [http://www.abridgegame.org/darcs/manual/node5.html#SECTION00520000000000000000 environment variables] may be added for example with 
+Changesets [1862] and [1863] introduced a `darcs` configuration section in the TracIni file. It allows the customization of the actual external command to execute (`command`), ~~the location of the cache directory (`cachedir`) to use instead of keeping it under repository's `_darcs` metadir~~. Another option is `dont_escape_8bit`, that basically adds `DARCS_DONT_ESCAPE_8BIT=1` as prefix to the command: other [http://www.abridgegame.org/darcs/manual/node5.html#SECTION00520000000000000000 environment variables] may be added for example with 
 {{{
 [darcs]