Merge branch 'master' of ssh://git-annex.branchable.com

2 files changed, 23 insertions, 0 deletions

diff --git a/doc/bugs/Enhancement:_git_annex_whereis_KEY.mdwn b/doc/bugs/Enhancement:_git_annex_whereis_KEY.mdwn
new file mode 100644
index 000000000..684a1e4fa
--- /dev/null
+++ b/doc/bugs/Enhancement:_git_annex_whereis_KEY.mdwn
@@ -0,0 +1,7 @@
+### Please describe the problem.
+
+Great work on git annex! One possible enhancement occured to me: It would be very useful though if the "whereis" command would support looking up the location of files by arbitrary keys. This way one could inspect the location of old content which is not currently checked-out in the tree.
+
+In a related vein, the "unused" command could report old filenames or describe the associated commits. Tracking old versions is a great feature of your git-based approach, but currently, tasks such as pruning selected content seem unwiedly. Though I might be missing existing solutions. You can easily "cut-off" the history by forcing a drop of all unused content. It would be cool if one could somehow "address" old versions by filename and commit/date and selectively drop just these. The same could go for the "whereis" command, where one could e.g. query which remote holds content which was stored under some filename at some specific date.
+
+Thanks Cheers!
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