Rev 61: Mention some existing bugs. in file:///home/vila/src/bzr/devnotes/

[Vincent Ladeuil]

At file:///home/vila/src/bzr/devnotes/

------------------------------------------------------------
revno: 61
revision-id: v.ladeuil+lp at free.fr-20110914092853-73r4u6l8cjcf3xyf
parent: v.ladeuil+lp at free.fr-20110823154000-ybhgp7o12emjnjhb
committer: Vincent Ladeuil <v.ladeuil+lp at free.fr>
branch nick: devnotes
timestamp: Wed 2011-09-14 11:28:53 +0200
message:
  Mention some existing bugs.
-------------- next part --------------
=== modified file 'configuration.txt'
--- a/configuration.txt	2011-08-23 15:40:00 +0000
+++ b/configuration.txt	2011-09-14 09:28:53 +0000
@@ -19,7 +19,7 @@
 ==============
 
 * Many parts of ``bzrlib`` declare constants and there is no way for the
-  user to look at or modify them.
+  user to look at or modify them (see bug #832061).
 
 * The current API requires a configuration object to create, modify or
   delete a configuration option in a given configuration file.  ``bzr
@@ -49,7 +49,7 @@
     section one and the location it applies to.
 
   * the default value (including calling any python code that may be
-    required to calculate this value),
+    required to calculate this value)(see bug #832064),
 
   * priority between sections in various config files
 
@@ -60,7 +60,7 @@
 * Access to the 'active' configuration option value from the command line
   doesn't give access to the specific section. (This is only a concern if
   the user has no other way to address a specific configuration option
-  including Store and Section when using ``bzr config``).
+  including Store and Section when using ``bzr config``) (see bug #725234).
 
 * Rules for configuration options are not clearly defined for remote
   branches (they may differ between dumb and smart servers the former will
@@ -96,7 +96,7 @@
   branch schemes like looms, pipeline, colocated branches and nested
   trees. Being able to specify options *in* a working tree could also help
   support conflict resolution options for a given file, directory or
-  subtree.
+  subtree (see bug #359320).
 
 * Since sections allow different definitions for the same option, a total
   order should be defined between sections to select the right definition for
@@ -117,7 +117,7 @@
   ``locations.conf`` for ``branch.conf``) are read every time *one* option is
   queried. Likewise, setting or deleting a configuration option implies
   writing the configuration file *immediately* after re-reading the file to
-  avoid racing updates.
+  avoid racing updates (see bug #832042).
 
 * The current implementation use a mix of transport-based and direct file
   systems operations (Addressed by Store implementation relying on