Added a comment
authoryarikoptic <yarikoptic@web>
Fri, 18 Sep 2020 20:11:27 +0000 (20:11 +0000)
committeradmin <admin@branchable.com>
Fri, 18 Sep 2020 20:11:27 +0000 (20:11 +0000)
doc/todo/make_git_check-ignore_less___34__cpu_heavy__34___while_addurl_--batch_--fast___63__/comment_3_2ebd0de2fe55230f4e589bd295c828a2._comment [new file with mode: 0644]

diff --git a/doc/todo/make_git_check-ignore_less___34__cpu_heavy__34___while_addurl_--batch_--fast___63__/comment_3_2ebd0de2fe55230f4e589bd295c828a2._comment b/doc/todo/make_git_check-ignore_less___34__cpu_heavy__34___while_addurl_--batch_--fast___63__/comment_3_2ebd0de2fe55230f4e589bd295c828a2._comment
new file mode 100644 (file)
index 0000000..b486c12
--- /dev/null
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="yarikoptic"
+ avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
+ subject="comment 3"
+ date="2020-09-18T20:11:25Z"
+ content="""
+thanks Joey.  I am yet to digest though if I would like (would be safe) to avoid `git check-ignore` call in general in my use-cases.  Originally I was wondering more about some kind of \"optimization\" ;) async --batch could help indeed, we just might need to change our code to support it (have not yet looked into the code)
+"""]]