diff options
Diffstat (limited to 'doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode2')
4 files changed, 0 insertions, 34 deletions
diff --git a/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode2/comment_1_3b6e4bd5ff1d6b35d6a894174e67835b._comment b/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode2/comment_1_3b6e4bd5ff1d6b35d6a894174e67835b._comment deleted file mode 100644 index 3ae4a4d04..000000000 --- a/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode2/comment_1_3b6e4bd5ff1d6b35d6a894174e67835b._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4" - subject="comment 1" - date="2015-07-28T20:20:04Z" - content=""" -d'oh -- I did file this one before! search on subject line wasn't productive though -- still can't find it. But you said that \"This is behaving as it's intended to.\" ... need to run -- will whine a bit more later in detail ;) -"""]] diff --git a/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode2/comment_2_29b9762ef3ad0c9e7abf8bf0d4eb6c42._comment b/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode2/comment_2_29b9762ef3ad0c9e7abf8bf0d4eb6c42._comment deleted file mode 100644 index 9c7b25013..000000000 --- a/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode2/comment_2_29b9762ef3ad0c9e7abf8bf0d4eb6c42._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4" - subject="3 modes (at user level of visibility) -> 2 modes" - date="2015-07-28T20:51:02Z" - content=""" -I am now not quite sure why I thought that in direct mode, regardless of OS we had somewhat consistent user experience across OSes: files either had content fetched by annex (thus not empty) or empty files, such as it is now on crippled filesystems. But really we have 3 modes now, depending on underlying files system (and not even user's decision) in direct mode we might have broken symlinks or empty files. Why bother with broken symlinks? just for performance reasons of not needing to rewrite them as empty files? -"""]] diff --git a/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode2/comment_3_9b76d5f67a858ea0170e816b35190aef._comment b/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode2/comment_3_9b76d5f67a858ea0170e816b35190aef._comment deleted file mode 100644 index 3c81b70b5..000000000 --- a/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode2/comment_3_9b76d5f67a858ea0170e816b35190aef._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-08-13T20:45:36Z" - content=""" -Broken symlinks are really much preferable to files that don't have the -content the user expects. Anyway, git-annex is just inheriting how git -deals with symlinks on filesystems that don't support them. - -Previous discussion: -<http://git-annex.branchable.com/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode/> -"""]] diff --git a/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode2/comment_4_d40ed7385eb46aa0a9940198e4591c0e._comment b/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode2/comment_4_d40ed7385eb46aa0a9940198e4591c0e._comment deleted file mode 100644 index d39513e32..000000000 --- a/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode2/comment_4_d40ed7385eb46aa0a9940198e4591c0e._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4" - subject="comment 4" - date="2015-08-19T20:50:08Z" - content=""" -gotcha -- thanks. Sticking to git behavior is indeed preferable. -Cheers! -"""]] |