aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar yarikoptic <yarikoptic@web>2018-02-07 20:01:53 +0000
committerGravatar admin <admin@branchable.com>2018-02-07 20:01:53 +0000
commite89c5b6310f20650d66aa8299b735dae71023bbd (patch)
treecc11f8dab67739b2b2087c4755c9472ab876017e
parent7ea3489ceb7dd201dc6dd01907f8c546f1bacbc1 (diff)
Added a comment
-rw-r--r--doc/design/exporting_trees_to_special_remotes/comment_21_062098e1f54b874467793e4487a45a9b._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/design/exporting_trees_to_special_remotes/comment_21_062098e1f54b874467793e4487a45a9b._comment b/doc/design/exporting_trees_to_special_remotes/comment_21_062098e1f54b874467793e4487a45a9b._comment
new file mode 100644
index 000000000..dfb5cb456
--- /dev/null
+++ b/doc/design/exporting_trees_to_special_remotes/comment_21_062098e1f54b874467793e4487a45a9b._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="yarikoptic"
+ avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
+ subject="comment 21"
+ date="2018-02-07T20:01:53Z"
+ content="""
+Ok, gotcha. Shouldn't then EXTENSION entries also be somehow versioned per each one of them? or if needed a new extension would be born by appending a version to its name (e.g. as with all those imap, imap2, imap3, ... ;-))
+"""]]