I couldn't find a "simple enough" solution to deal with that, so I moved to emulated Linux [1].
I don't know if the long file path is a limitation of Windows itself or libgit2. Because if it's the former, then I'll try this setting in Windows 10 and let you know if it works: https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/ Regards! Esteban A. Maringolo El mié., 6 mar. 2019 a las 13:19, Sean P. DeNigris (<s...@clipperadams.com>) escribió: > > Tim Mackinnon wrote > > how is this shared repository supposed to work? > > While I initially liked the space efficiency of the shared approach, I > eventually gave up because it created too many (often obscure) problems. It > just doesn't seem to be a good match for git, although you can get away with > it in the simplest cases (read-only, no branch switching). It sounds like > you may not have the luxury of avoiding it so hopefully someone can provide > more constructive help. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >