From 51c40fc985176c28d17ef6fc0370d259949f688a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 5 Dec 2017 13:28:07 -0400 Subject: yet another instance of git smudge/clean interface suck --- ...comment_1_c42743828ddc62f7df7f612c713ee309._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/bugs/Adjust_--unlock_not_using_--reflink__63__/comment_1_c42743828ddc62f7df7f612c713ee309._comment (limited to 'doc') diff --git a/doc/bugs/Adjust_--unlock_not_using_--reflink__63__/comment_1_c42743828ddc62f7df7f612c713ee309._comment b/doc/bugs/Adjust_--unlock_not_using_--reflink__63__/comment_1_c42743828ddc62f7df7f612c713ee309._comment new file mode 100644 index 000000000..e30471b84 --- /dev/null +++ b/doc/bugs/Adjust_--unlock_not_using_--reflink__63__/comment_1_c42743828ddc62f7df7f612c713ee309._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2017-12-05T17:24:24Z" + content=""" +What happens is `git annex adjust` creates a branch and runs `git checkout` +to check it out. Then git calls `git-annex smudge` on files, and +unfortunately the git smudge interface requires that git-annex output the +whole content of the file, to stdout, which git then writes to disk. + +So yes, this doesn't use reflinks, but it's worse than that, a better +interface would let git-annex simply move or hard-link the file into place, +even on filesystems not supporting reflinks. + +This is discussed in detail in [[todo/smudge]]. Unfortunately it will need +a better interface in git to be addressed, and that's why v6 is still an +experimental feature. +"""]] -- cgit v1.2.3