From 6e6a90805d347d5579ea8b2fed1b389cbf8e7f76 Mon Sep 17 00:00:00 2001 From: Michel Date: Thu, 2 Mar 2017 09:20:15 +0000 Subject: [PATCH 1/4] --- .../Empty_files_make_git_status_slow.mdwn | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 doc/bugs/Empty_files_make_git_status_slow.mdwn diff --git a/doc/bugs/Empty_files_make_git_status_slow.mdwn b/doc/bugs/Empty_files_make_git_status_slow.mdwn new file mode 100644 index 0000000000..f8438f4ef0 --- /dev/null +++ b/doc/bugs/Empty_files_make_git_status_slow.mdwn @@ -0,0 +1,26 @@ +### Please describe the problem. + +When empty files are committed to a repository, git status becomes slow because git annex smudge is run for every empty file under git annex even with clean HEAD. I know git annex is for large files (rather than infinity small ones), but I'm using it to manage a GRASS GIS database, which oddly uses empty files for some things:/ + +### What steps will reproduce the problem? +``` +# slow +touch emptyfile +git add emptyfile +git commit -a -m 'Added empty file.' +GIT_TRACE=1 git status + +# fast +cat 1 > emptyfile +git commit -a -m 'Added a 1 to emptyfile.' +GIT_TRACE=1 git status +``` + +### What version of git-annex are you using? On what operating system? +- git-annex version: 6.20170228-g7a32e08c4 +- operating system: linux x86_64 (SLE 12.2) +- local repository version: 6 + + +### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) +Yes, git with git annex has revolutionised my scientific project file organisation and thats why I want to improve it. From fcdc72f8077056e1aa9a667efb6062313eb9e115 Mon Sep 17 00:00:00 2001 From: "git-annex@31849d241f10c295b30a9707352ae5c7d743adb7" Date: Thu, 2 Mar 2017 16:14:52 +0000 Subject: [PATCH 2/4] Added a comment --- .../comment_1_01363d4b41dcbebc9bcff7b956c03091._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/todo/wishlist__58___Parity_files_for_encrypted_remotes/comment_1_01363d4b41dcbebc9bcff7b956c03091._comment diff --git a/doc/todo/wishlist__58___Parity_files_for_encrypted_remotes/comment_1_01363d4b41dcbebc9bcff7b956c03091._comment b/doc/todo/wishlist__58___Parity_files_for_encrypted_remotes/comment_1_01363d4b41dcbebc9bcff7b956c03091._comment new file mode 100644 index 0000000000..c04f2f4ebe --- /dev/null +++ b/doc/todo/wishlist__58___Parity_files_for_encrypted_remotes/comment_1_01363d4b41dcbebc9bcff7b956c03091._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="git-annex@31849d241f10c295b30a9707352ae5c7d743adb7" + nickname="git-annex" + avatar="http://cdn.libravatar.org/avatar/180f1a763647bfc099e97ac88b8f7b37" + subject="comment 1" + date="2017-03-02T16:14:51Z" + content=""" +If you're generating parity files for the content anyway, why not encrypt locally, generate parity files for the encrypted content, then check that in to git-annex? +"""]] From 273decc078c8b2d16d553204795afe8dbdabb455 Mon Sep 17 00:00:00 2001 From: "git-annex@31849d241f10c295b30a9707352ae5c7d743adb7" Date: Thu, 2 Mar 2017 16:15:44 +0000 Subject: [PATCH 3/4] removed --- .../comment_1_01363d4b41dcbebc9bcff7b956c03091._comment | 9 --------- 1 file changed, 9 deletions(-) delete mode 100644 doc/todo/wishlist__58___Parity_files_for_encrypted_remotes/comment_1_01363d4b41dcbebc9bcff7b956c03091._comment diff --git a/doc/todo/wishlist__58___Parity_files_for_encrypted_remotes/comment_1_01363d4b41dcbebc9bcff7b956c03091._comment b/doc/todo/wishlist__58___Parity_files_for_encrypted_remotes/comment_1_01363d4b41dcbebc9bcff7b956c03091._comment deleted file mode 100644 index c04f2f4ebe..0000000000 --- a/doc/todo/wishlist__58___Parity_files_for_encrypted_remotes/comment_1_01363d4b41dcbebc9bcff7b956c03091._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="git-annex@31849d241f10c295b30a9707352ae5c7d743adb7" - nickname="git-annex" - avatar="http://cdn.libravatar.org/avatar/180f1a763647bfc099e97ac88b8f7b37" - subject="comment 1" - date="2017-03-02T16:14:51Z" - content=""" -If you're generating parity files for the content anyway, why not encrypt locally, generate parity files for the encrypted content, then check that in to git-annex? -"""]] From 2468e69354dd5b9ab2196a2c7bce6d73e5fd2ba3 Mon Sep 17 00:00:00 2001 From: "git-annex@31849d241f10c295b30a9707352ae5c7d743adb7" Date: Thu, 2 Mar 2017 16:16:05 +0000 Subject: [PATCH 4/4] Added a comment --- .../comment_1_5fbffd74f9d89857b807093cd7a5941e._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/todo/wishlist__58___Parity_files_for_encrypted_remotes/comment_1_5fbffd74f9d89857b807093cd7a5941e._comment diff --git a/doc/todo/wishlist__58___Parity_files_for_encrypted_remotes/comment_1_5fbffd74f9d89857b807093cd7a5941e._comment b/doc/todo/wishlist__58___Parity_files_for_encrypted_remotes/comment_1_5fbffd74f9d89857b807093cd7a5941e._comment new file mode 100644 index 0000000000..b440d64d2f --- /dev/null +++ b/doc/todo/wishlist__58___Parity_files_for_encrypted_remotes/comment_1_5fbffd74f9d89857b807093cd7a5941e._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="git-annex@31849d241f10c295b30a9707352ae5c7d743adb7" + nickname="git-annex" + avatar="http://cdn.libravatar.org/avatar/180f1a763647bfc099e97ac88b8f7b37" + subject="comment 1" + date="2017-03-02T16:16:05Z" + content=""" +If you're generating parity files for the content anyway, why not encrypt locally, generate parity files for the encrypted content, then check that in to git-annex? +"""]]