From ae3beccd7c68d3f855e69cc75a905dfbb01d2d99 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 3 Dec 2018 13:07:40 -0400 Subject: [PATCH] comment --- ...ment_1_24d303ada8bedff1744dc30ad136a265._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/todo/LFS_API_support/comment_1_24d303ada8bedff1744dc30ad136a265._comment diff --git a/doc/todo/LFS_API_support/comment_1_24d303ada8bedff1744dc30ad136a265._comment b/doc/todo/LFS_API_support/comment_1_24d303ada8bedff1744dc30ad136a265._comment new file mode 100644 index 0000000000..20f9a698a4 --- /dev/null +++ b/doc/todo/LFS_API_support/comment_1_24d303ada8bedff1744dc30ad136a265._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2018-12-03T17:00:42Z" + content=""" +I think it's possible to write such an external special remote. +You would need to generate the hashes that git-lfs uses +to store files and have git-annex remember them for retrieval, using +SETSTATE and GETSTATE. + +(IIRC git-lfs uses SHA256, so when a git-annex key also does, which is +common, you could special case it to avoid needing to store state.) +"""]]