diff options
| author |  kubaello@d561f15ff5c07a78b706b096375cd89d6d706066 <kubaello@web> | 2017-03-16 01:22:44 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2017-03-16 01:22:44 +0000 |
| commit | 00d21b7a5b2f15fee2dc2e8104ba6320e15cfa09 (patch) | |
| tree | b74a52ae58785c064e6f81daa153f3c6fc7c7bea | |
| parent | 3821e3aa3ba061fdb6ac31964d14a5a8141a2def (diff) | |
Added a comment
| -rw-r--r-- | doc/bugs/Excessively_long_temp_names_preventing___34__get__34___on_Windows/comment_2_7d691fe40bb134d0f270ed3a9cfbf659._comment | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/bugs/Excessively_long_temp_names_preventing___34__get__34___on_Windows/comment_2_7d691fe40bb134d0f270ed3a9cfbf659._comment b/doc/bugs/Excessively_long_temp_names_preventing___34__get__34___on_Windows/comment_2_7d691fe40bb134d0f270ed3a9cfbf659._comment new file mode 100644 index 000000000..7ba073402 --- /dev/null +++ b/doc/bugs/Excessively_long_temp_names_preventing___34__get__34___on_Windows/comment_2_7d691fe40bb134d0f270ed3a9cfbf659._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="kubaello@d561f15ff5c07a78b706b096375cd89d6d706066" + nickname="kubaello" + avatar="http://cdn.libravatar.org/avatar/df2d1d9871b92552b99c3bacf442d739" + subject="comment 2" + date="2017-03-16T01:22:44Z" + content=""" +I came across the same problem today and I think I've found a workaround: [long paths on windows 10 - workaround](https://git-annex.branchable.com/forum/long_paths_on_windows_10_-_workaround/). It turns out Windows 10 allows enabling support for long paths with a single registry modification - unfortunately it is a system level setting, so it can potentially break some other programs. +"""]] |