From 389b8726fcd26ad5c46c6805c04cddd379272baf Mon Sep 17 00:00:00 2001 From: "xvorsx@a3fc1a0cf228782f624e5eb21ba8a664227b6c60" Date: Mon, 7 Aug 2023 07:20:55 +0000 Subject: [PATCH] removed --- ...nt_4_c455bc3ce6d8a38869282f3a85ccc937._comment | 15 --------------- 1 file changed, 15 deletions(-) delete mode 100644 doc/forum/Git_filters__58___smudgeToFile_and_cleanFromFile/comment_4_c455bc3ce6d8a38869282f3a85ccc937._comment diff --git a/doc/forum/Git_filters__58___smudgeToFile_and_cleanFromFile/comment_4_c455bc3ce6d8a38869282f3a85ccc937._comment b/doc/forum/Git_filters__58___smudgeToFile_and_cleanFromFile/comment_4_c455bc3ce6d8a38869282f3a85ccc937._comment deleted file mode 100644 index 7cf96407e9..0000000000 --- a/doc/forum/Git_filters__58___smudgeToFile_and_cleanFromFile/comment_4_c455bc3ce6d8a38869282f3a85ccc937._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="xvorsx@a3fc1a0cf228782f624e5eb21ba8a664227b6c60" - nickname="xvorsx" - avatar="http://cdn.libravatar.org/avatar/f8a11fb3152e472307bde487d188b23a" - subject="comment 4" - date="2023-08-07T07:19:46Z" - content=""" -Thank you for the reference! - -I may try to use this trick, but I doubt it would be sufficient for me: - -> To avoid the problem, git-annex smudge --clean relies on a not very well documented trick: It is fed a possibly large file on stdin, but when it closes the FD without reading. git gets a SIGPIPE and stops reading and sending the file. Instead of reading from stdin, git-annex abuses the fact that git provides the clean filter with the work tree filename, and reads and cleans the file itself, more efficiently. - -I will keep you updated on the progress in this direction. -"""]]