diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-09-21 13:05:44 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-09-21 13:05:44 -0400 |
| commit | 7ea332f43e0f3e5f565714ef250ae8413a3ddbb9 (patch) | |
| tree | b8de127db0b6d836ea4087e85628e153193be3ed | |
| parent | d3d55029d3adfe126f723cb1312f477dce921534 (diff) | |
webapp: Remove the "disable remote" feature from the UI.
It's confusing, easy to select by accident and get into a situation the
webapp offers no easy recovery from, and pausing syncing works just as well
in most situations.
| -rw-r--r-- | debian/changelog | 1 | ||||
| -rw-r--r-- | doc/forum/webapp:_disabling_a_paired_repository/comment_2_28cf58629b9774426c084d80964151d7._comment | 19 |
2 files changed, 20 insertions, 0 deletions
diff --git a/debian/changelog b/debian/changelog index e13e648e4..3ec572d04 100644 --- a/debian/changelog +++ b/debian/changelog @@ -3,6 +3,7 @@ git-annex (5.20150917) UNRELEASED; urgency=medium * info: Don't allow use in a non-git-annex repository, since it uses the git-annex branch and would create it if it were missing. * assistant: When updating ~/.ssh/config, preserve any symlinks. + * webapp: Remove the "disable remote" feature from the UI. -- Joey Hess <id@joeyh.name> Wed, 16 Sep 2015 12:23:33 -0400 diff --git a/doc/forum/webapp:_disabling_a_paired_repository/comment_2_28cf58629b9774426c084d80964151d7._comment b/doc/forum/webapp:_disabling_a_paired_repository/comment_2_28cf58629b9774426c084d80964151d7._comment new file mode 100644 index 000000000..5d78439b6 --- /dev/null +++ b/doc/forum/webapp:_disabling_a_paired_repository/comment_2_28cf58629b9774426c084d80964151d7._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2015-09-21T16:55:47Z" + content=""" +Disabling a remote is a weak form of deleting it; the remote repository is +left as-is, but the git remote is removed so git-annex won't sync with it, +and the webapp won't show it. + +I don't know if it makes sense for the webapp to expose this possibility. +It seems that it certianly doesn't makes sense to do it without getting +confirmation, since to re-enable the repository, the user has to do some +probably unknown to them process to set it back up. + +In your case, I think that re-doing the pairing process would get them back +to how they were. + +On consideration, I am going to remove this feature from the webapp UI. +"""]] |