summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-10-27 18:59:25 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-10-27 18:59:25 -0400
commit2888562724acd06ed2acd5c5a318a88d9e33d484 (patch)
tree80359610787d92d1635d73743f87134dc54226f9
parentb955238ec7464b12c793d543fc51308c8b213e08 (diff)
update
-rw-r--r--doc/bugs/wishlist:_support_drop__44___find_on_special_remotes.mdwn11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/bugs/wishlist:_support_drop__44___find_on_special_remotes.mdwn b/doc/bugs/wishlist:_support_drop__44___find_on_special_remotes.mdwn
index 2dc735e99..982f398ae 100644
--- a/doc/bugs/wishlist:_support_drop__44___find_on_special_remotes.mdwn
+++ b/doc/bugs/wishlist:_support_drop__44___find_on_special_remotes.mdwn
@@ -1,6 +1,17 @@
Currently there is no way to drop files, or list what files are available, on a special remote.
It would be good if "git annex drop" and "git annex find" supported the --from argument.
+> I agree, drop should support --from.
+>
+> To find files *believed* to be present in a given remote, use
+> `git annex find --in remote`
+> Note that it might show out of date info, since it does not actually go
+> check the current contents of the remote. The only reason to support
+> `find --from` would be to always check, but I don't think that's needed.
+> --[[Joey]]
+
For commands that don't support the --from argument, it would also be nice to print an error.
Currently running "git annex drop --from usbdrive" doesn't behave as hoped and instead drops
all content from the local annex.
+
+> This is done now. --[[Joey]]