diff options
author | janis_e <janis_e@web> | 2015-01-29 08:36:48 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2015-01-29 08:36:48 +0000 |
commit | 9387f30b3851c493e13a8483590722dea401bb4f (patch) | |
tree | a0c1cfbb084d9bf591591d64029852e29e6a0b65 | |
parent | 60e3e2509878b35b22935164983aebfdf41357bb (diff) |
-rw-r--r-- | doc/forum/Is_there_any_delta_handling_for_file_modifications__63__.mdwn | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/forum/Is_there_any_delta_handling_for_file_modifications__63__.mdwn b/doc/forum/Is_there_any_delta_handling_for_file_modifications__63__.mdwn new file mode 100644 index 000000000..30463a496 --- /dev/null +++ b/doc/forum/Is_there_any_delta_handling_for_file_modifications__63__.mdwn @@ -0,0 +1,20 @@ +Hi! + +I have few large files, which will be slightly modified from time to time. Consider the following example: + + $ git init + $ git annex init "somerepo" + $ dd if=/dev/urandom of=foo bs=50M count=1 + $ git annex add foo + $ git commit -m "foo added" + $ git annex unlock foo + $ echo "modification" >> foo + $ git annex add foo + $ git -m commit "modification 1 of foo" + $ echo "another modification" >> foo + $ git annex add foo + $ git -m commit "modification 2 of foo" + +I would have expected ending up with a full copy of foo, and a delta storage for the first version and the first modification. Instead, three full-sized copies are created within the .git/annex/objects directory, even though the modifications only added a few characters. + +Is there any way to not always store a full copy of each file for each modification, but only a delta? |