Greetings,
It seems there is a local solution by changing a git settings or two ( see
https://stackoverflow.com/questions/22575662/filename-too-long-in-git-for-windows
).
Given that there's a workaround, I'm more hesitant about proposing a PR as
it can be fixed locally (though might require admin
Would it be too crazy to shrink down some offending name to prevent
error when switching to more recent branches? I can submit a PR if needed.
Seems like a good idea. You'll likely have to change references to that
file in the test suite.
--
http://www.spatialys.com
My software is free, bu
Windows has fairly shorter path limitation by default (see
https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry
)
Alex
Le jeu. 24 nov. 2022 à 20:33, Greg Troxel via QGIS-Developer <
qgis-developer@lists.osgeo.org> a écrit :
>
> "Alexis R.L. via QGIS
"Alexis R.L. via QGIS-Developer"
writes:
> I'm not sure it warranted a bug report but some control image now have
> names that are frankly too long and are causing issues in git if the local
> report folder is located some level down.
>
> Would it be too crazy to shrink down some offending name
Greetings everyone,
I'm not sure it warranted a bug report but some control image now have
names that are frankly too long and are causing issues in git if the local
report folder is located some level down.
Would it be too crazy to shrink down some offending name to prevent error
when switching
