Rev 52: One more example in file:///home/vila/src/bzr/devnotes/

[Vincent Ladeuil]

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

------------------------------------------------------------
revno: 52
revision-id: v.ladeuil+lp at free.fr-20110513101052-zq3swtqj0tat956w
parent: v.ladeuil+lp at free.fr-20110513092452-4ettxgxz575cnkfx
committer: Vincent Ladeuil <v.ladeuil+lp at free.fr>
branch nick: devnotes
timestamp: Fri 2011-05-13 12:10:52 +0200
message:
  One more example
-------------- next part --------------
=== modified file 'configuration.txt'
--- a/configuration.txt	2011-05-13 09:24:52 +0000
+++ b/configuration.txt	2011-05-13 10:10:52 +0000
@@ -570,7 +570,18 @@
 * [BOOKMARKS] section can be replaced by ``bookmarks.xxx`` options (the
   bookmarks plugins already uses ``bookmarks_xxx`` in branch.conf since no
   sections were supported there). This could be automated by creating the
-  corresponding options ?
+  corresponding options ? An alternative would be to just implement a
+  'config:' directory service so any option can be used as a bookmark. This
+  allows things like::
+
+    [/whatever/path]
+    my_push = lp:<launchpad.login>/xxx/{nick}
+    web_site=ftp://example.com/
+
+    bzr push config:web_site
+
+  Which means we completely replace the plugin and don't need to care about
+  migrating the section.
 
 * [ALIASES] section can be replaced by corresponding bzr.alias.xxx
   options. This could be automated by creating the corresponding options ?