014-11-15 17:57 GMT+01:00  <org.fossil-scm.fossil-us...@io7m.com>:
> 'Lo.
>
> I seem to have run into a problem that I can reproduce with the
> following repository:
>
>   http://waste.io7m.com/2014/11/15/fossil-pathbug.fossil
>
> The repository contains a directory "b" full of files, and a directory
> "a" containing about 256 nested directories, with a single file at the
> deepest point.

The win32 api has limitations:
    <http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx#maxpath>

For absolute paths it is possible to workaround this (which fossil does), but
for relative paths that's a more difficult story. A possible solution might
be to translate relative paths to absolute paths (with extended path
prefix) if they contain more than 260 characters, but it is not trivial
to get this right. Is it really worth it? (if you can convince me that
it's worth it, maybe I implement it some day ...... )

Regards,
     Jan Nijtmans
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to