From b891720284065e47e41591b08897175c91c5f8cb Mon Sep 17 00:00:00 2001 From: divB Date: Fri, 9 May 2014 06:06:54 +0000 Subject: [PATCH] Added a comment --- ...t_3_3436e26dd9fe07233a070d4e95d81cdf._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/Problems_when_cloning_a_repository/comment_3_3436e26dd9fe07233a070d4e95d81cdf._comment diff --git a/doc/forum/Problems_when_cloning_a_repository/comment_3_3436e26dd9fe07233a070d4e95d81cdf._comment b/doc/forum/Problems_when_cloning_a_repository/comment_3_3436e26dd9fe07233a070d4e95d81cdf._comment new file mode 100644 index 0000000000..65470841a5 --- /dev/null +++ b/doc/forum/Problems_when_cloning_a_repository/comment_3_3436e26dd9fe07233a070d4e95d81cdf._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="divB" + ip="171.67.174.99" + subject="comment 3" + date="2014-05-09T06:06:54Z" + content=""" +Finally I found it: https://git-annex.branchable.com/bugs/assistant_doesn__39__t_sync_empty_directories/ + +Empty directories. + +Wow! I was not aware that git is actually a step BACKWARDS in this regard :-( + +That was already a big problem half a century ago in CVS, finally fixed in SVN and git re-introduces the issue? Sad :-( + + +"""]]