diff options
| author |  https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4 <https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4@web> | 2015-07-28 20:51:02 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-07-28 20:51:02 +0000 |
| commit | cdfea08af025e6b544e8868bcc96c9e2ff07e272 (patch) | |
| tree | d15a97097147400611b0e6c06b2a25f4dc534e76 | |
| parent | c6cc959c6dc87296f033b4a19149bebb4467cce2 (diff) | |
Added a comment: 3 modes (at user level of visibility) -> 2 modes
| -rw-r--r-- | doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode2/comment_2_29b9762ef3ad0c9e7abf8bf0d4eb6c42._comment | 7 |
1 files changed, 7 insertions, 0 deletions
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 new file mode 100644 index 000000000..9c7b25013 --- /dev/null +++ b/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode2/comment_2_29b9762ef3ad0c9e7abf8bf0d4eb6c42._comment @@ -0,0 +1,7 @@ +[[!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? +"""]] |