From d521220e0e670ee56e57d152b033c7768b7e86f6 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Thu, 20 Feb 2020 19:23:07 +0000 Subject: [PATCH] Added a comment: backends vs special remotes --- ...omment_31_32df8ec41dd8a6516b88b1871c998eb9._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/backends/comment_31_32df8ec41dd8a6516b88b1871c998eb9._comment diff --git a/doc/backends/comment_31_32df8ec41dd8a6516b88b1871c998eb9._comment b/doc/backends/comment_31_32df8ec41dd8a6516b88b1871c998eb9._comment new file mode 100644 index 0000000000..c53c2276f0 --- /dev/null +++ b/doc/backends/comment_31_32df8ec41dd8a6516b88b1871c998eb9._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="backends vs special remotes" + date="2020-02-20T19:23:04Z" + content=""" +@annex2384 \"Backend which doesn't store files at all?\" -- are you sure you're thinking of backends and not of [[special_remotes]]? Backends don't \"store files\", special remotes do. Backends create keys identifying specific contents. + +Not sure I fully understand your use case, but you could write an [[external special remote|special_remotes/external]] that, for a given git-annex key, stores \"the location of possible local copies of the file\" -- e.g. using `SETSTATE` or `SETURIPRESENT`. +"""]]