summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar zardoz <zardoz@web>2014-01-23 12:55:21 +0000
committerGravatar admin <admin@branchable.com>2014-01-23 12:55:21 +0000
commitf7611e712a7e7832894133119d1933204f894513 (patch)
treeb0ea33406a9fa51a6d06895b786ba2b432f71a8e
parent96323a4241172e010930d461a10a5771eb06cc0f (diff)
-rw-r--r--doc/bugs/Unused_files_not_being_reported:_Do_not_take_remote_tracking_branches_into_account__63__.mdwn16
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/bugs/Unused_files_not_being_reported:_Do_not_take_remote_tracking_branches_into_account__63__.mdwn b/doc/bugs/Unused_files_not_being_reported:_Do_not_take_remote_tracking_branches_into_account__63__.mdwn
new file mode 100644
index 000000000..011089131
--- /dev/null
+++ b/doc/bugs/Unused_files_not_being_reported:_Do_not_take_remote_tracking_branches_into_account__63__.mdwn
@@ -0,0 +1,16 @@
+### Please describe the problem.
+After branching from master/HEAD^ and deleting the master branch, I was surprised that content introduced in master/HEAD is not reported as unused. Instead, one first has to delete the synced/master branch, and also the remote-tracking branches for master.
+
+Would it make sense to discount synced/* and the remote tracking branches when gathering unused files? If the remote-tracking branch always reflects the state of the remote, tracking a branch should not cause annex to think that the local annex is somehow using all the files on the remote. Or would that be unsafe? As for the synced/* branches I'm not so sure.
+
+### What steps will reproduce the problem?
+Clone annex A to B.
+Branch off of master^ in B.
+Delete master.
+Issue git annex unused. --> Content introduced in master is still not reported as unused.
+Delete synced/master --> Cf. above.
+Delete origin/master and origin/synced/master --> Content is now reported as unused.
+
+### What version of git-annex are you using? On what operating system?
+
+5.20131230