From b2a2bc9597d3061817da3ad1d5c375ce739991f2 Mon Sep 17 00:00:00 2001 From: kyle Date: Tue, 24 Sep 2019 18:10:16 +0000 Subject: [PATCH] Added a comment: git docs on "%f" --- .../comment_4_ef42e80aac54e02000c1a61b1f42aed0._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/git_smudge_clean_interface_suboptiomal/comment_4_ef42e80aac54e02000c1a61b1f42aed0._comment diff --git a/doc/todo/git_smudge_clean_interface_suboptiomal/comment_4_ef42e80aac54e02000c1a61b1f42aed0._comment b/doc/todo/git_smudge_clean_interface_suboptiomal/comment_4_ef42e80aac54e02000c1a61b1f42aed0._comment new file mode 100644 index 0000000000..8edb2cffb9 --- /dev/null +++ b/doc/todo/git_smudge_clean_interface_suboptiomal/comment_4_ef42e80aac54e02000c1a61b1f42aed0._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="kyle" + avatar="http://cdn.libravatar.org/avatar/7d6e85cde1422ad60607c87fa87c63f3" + subject="git docs on "%f"" + date="2019-09-24T18:10:16Z" + content=""" +Ilya, the patch that added the text you quote (52db4b0467, clarify %f documentation, 2016-07-11) was written by Joey, so I think it's safe to say that git-annex filters don't rely on \"%f\" being an actual file on disk. +"""]]