From: public_vi@tut.by
To: git@vger.kernel.org
Cc: public_vi@tut.by
Subject: [PATCH] contrib: Add "external blob storage" clean and smudge filters
Date: Wed, 21 Jul 2010 04:07:31 +0300 [thread overview]
Message-ID: <1279674451-13143-1-git-send-email-public_vi@tut.by> (raw)
From: Vitaly _Vi Shukela <public_vi@tut.by>
Proof-of-concept "external storage" for big blobs using filters.
This is rather high-impact thing, expect a great slowdown or other
inconsistencies
Files are uploaded on a server each time Git attempts to read them
When checking out, files are downloaded from the server, so it should be
mostly transparent for user (except of slowness)
SHA-1 hashes are stored in Git instead of actual file content
Signed-off-by: Vitaly _Vi Shukela <public_vi@tut.by>
---
contrib/filters/external_blob_storage.config | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
create mode 100644 contrib/filters/external_blob_storage.config
diff --git a/contrib/filters/external_blob_storage.config b/contrib/filters/external_blob_storage.config
new file mode 100644
index 0000000..054eb38
--- /dev/null
+++ b/contrib/filters/external_blob_storage.config
@@ -0,0 +1,11 @@
+# Proof-of-concept "external storage" for big blobs using filters.
+# This is rather high-impact thing, expect a great slowdown or other inconsistencies
+
+# Put strings like "*.avi filter=external_blob_storage" to your .gitattributes or .git/info/attributes files,
+# and that files will be uploaded on server (test@127.0.0.1) each time Git attempts to read them (git add, git diff, git status, ...)
+# When checking out, files will be downloaded from server.
+# SHA-1 hashes are stored in Git instead of actual file content
+
+[filter "external_blob_storage"]
+ clean = ssh test@127.0.0.1 'tee qqq | sha1sum | awk \"{print \\$1}\" | (read S && mv qqq \"$S\" && echo \"$S\" )'
+ smudge = ssh test@127.0.0.1 'read S && cat \"$S\"'
--
1.7.1
reply other threads:[~2010-07-21 1:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1279674451-13143-1-git-send-email-public_vi@tut.by \
--to=public_vi@tut.by \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).