remotenames: mark the extension as EXPERIMENTAL
I still don't feel confident about locking the behavior of all the things in
the remotenames extension. Moreover the extension was introduced in this cycle
only. Let's mark this extension EXPERIMENTAL for now so that we can change
things especially the storage layer if required in next cycle.
I will like to use cbor at storage layer too.
Differential Revision: https://phab.mercurial-scm.org/D3426
--- a/hgext/remotenames.py Tue Apr 24 22:47:14 2018 -0400
+++ b/hgext/remotenames.py Wed Apr 25 00:26:49 2018 +0530
@@ -6,7 +6,7 @@
# This software may be used and distributed according to the terms of the
# GNU General Public License version 2 or any later version.
-""" showing remotebookmarks and remotebranches in UI
+""" showing remotebookmarks and remotebranches in UI (EXPERIMENTAL)
By default both remotebookmarks and remotebranches are turned on. Config knob to
control the individually are as follows.
--- a/tests/test-help.t Tue Apr 24 22:47:14 2018 -0400
+++ b/tests/test-help.t Wed Apr 25 00:26:49 2018 +0530
@@ -278,7 +278,6 @@
purge command to delete untracked files from the working
directory
relink recreates hardlinks between repository clones
- remotenames showing remotebookmarks and remotebranches in UI
schemes extend schemes with shortcuts to repository swarms
share share a common history between several working directories
shelve save and restore changes to the working directory