summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawncBlzaDI248OZGjKQMXrLVQIx4XrZrzFo <Perttu@web>2012-06-19 07:08:44 +0000
committerGravatar admin <admin@branchable.com>2012-06-19 07:08:44 +0000
commite986d1acb1c335958805797e40a2ef79bf1e1e43 (patch)
tree0f26d611026fe76fc9ba3c7e1d4ae3136f76abef
parentd4e5affec03fce1f6a169a5dc29403393422514d (diff)
-rw-r--r--doc/forum/Wishlist:_automatic_reinject.mdwn14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/forum/Wishlist:_automatic_reinject.mdwn b/doc/forum/Wishlist:_automatic_reinject.mdwn
new file mode 100644
index 000000000..f975c7521
--- /dev/null
+++ b/doc/forum/Wishlist:_automatic_reinject.mdwn
@@ -0,0 +1,14 @@
+I think it would be useful to supplement the `reinject` command with an automatic
+mode which calculates the checksum of the source file and injects the file if it
+is known to the repository (without the need to provide a destination filename).
+In addition, this could be done recursively if the user provides a directory to
+inject. All this can probably be done already with some plumbing, but a simple
+`reinject --auto` (or `scour`, or `scavenge`, if you like) would be a nice addition.
+Of course this would only work for the checksum backends.
+
+Example use cases would be:
+
+* Recovering data from lost+found easily
+* Making use of old (pre-git-annex) archival volumes with useful files
+ scattered among non-useful files
+* Sneaker-netting files between disconnected git-annex repositories