summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawmYMS6tQ8q9k1fylGyA9Q6fdFzRBotME2Q <tom@web>2014-06-03 14:44:34 +0000
committerGravatar admin <admin@branchable.com>2014-06-03 14:44:34 +0000
commiteb71a12c30ed8a25033fa5c21834daba6e8adb14 (patch)
tree62152eea40722fcc3d49ea907cd1df6e7a5f78bb
parent7efce5a945e5578c94b1b3e26f482a8fe36f2cf6 (diff)
question on view branches behaviour: they never get deleted, why?
-rw-r--r--doc/forum/views___40__branches__41___never_get_deleted.mdwn12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/forum/views___40__branches__41___never_get_deleted.mdwn b/doc/forum/views___40__branches__41___never_get_deleted.mdwn
new file mode 100644
index 000000000..d8b071014
--- /dev/null
+++ b/doc/forum/views___40__branches__41___never_get_deleted.mdwn
@@ -0,0 +1,12 @@
+Hello everyone,
+I would like to know if this is normal behavior or if it's a problem with my repository:
+
+Whenever I set a view with
+
+git annex view attr="\*"'
+
+a new branch representing the selected view gets created, as expected. The problem is that when I switch back to master ('git checkout master' or even 'git annex vpop') the view branch stays there, and all subsequent operations on the annex also consider the view branch, resulting a great slowdown if one has done many views (attr="this", attr="that", etc.). Is this normal? If so, why is it necessary for the branch to stay on? Does it speed up going back to the branch? Redoing git annex view attr="*" does not seem to take less time.
+
+Am I doing it wrong? Should I be deleting used view branches on my own? How?
+
+thanks for your replies.