Rev 6501: Mention that a given config option cannot be safely handled via both APIs at the same time. in file:///home/vila/src/bzr/bugs/948339-config-caching/

Vincent Ladeuil v.ladeuil+lp at free.fr
Tue Mar 13 16:42:21 UTC 2012


At file:///home/vila/src/bzr/bugs/948339-config-caching/

------------------------------------------------------------
revno: 6501
revision-id: v.ladeuil+lp at free.fr-20120313164220-atkou2zprhlspmwg
parent: v.ladeuil+lp at free.fr-20120313162830-83ekrd4ghqru0whh
committer: Vincent Ladeuil <v.ladeuil+lp at free.fr>
branch nick: 948339-config-caching
timestamp: Tue 2012-03-13 17:42:20 +0100
message:
  Mention that a given config option cannot be safely handled via both APIs at the same time.
-------------- next part --------------
=== modified file 'doc/developers/configuration.txt'
--- a/doc/developers/configuration.txt	2012-01-28 15:37:27 +0000
+++ b/doc/developers/configuration.txt	2012-03-13 16:42:20 +0000
@@ -98,6 +98,13 @@
 * convert the unicode string provided by the user into a suitable
   representation (integer, list, etc).
 
+If you start migrating a given option to the config stacks, don't stop
+mid-way, all its uses should be covered (tests included). There are some
+edge cases where updates via one API will be not be seen by the other API
+(see http://pad.lv/948339 and http://pad.lv/948344 for details). Roughly,
+the old API always trigger an IO while the new one cache values to avoid
+them. This works fine as long as a given option is handled via a single API.
+
 Adding a new stack
 ------------------
 



More information about the bazaar-commits mailing list