I have not experienced any problems like that myself, but
when searching for online documentation for recursive
unversioned insertion of files, id est I wanted to
use the
fossil unversioned add
recursively without it telling me that paths with "./" like
fossil unversioned add ./foo/bar_01
fossil unversioned add ./foo/bar_02
are, I quote: "not an acceptable filename"
---You-may-skip-reading-this-citation--but-here-it--starts---
ts2@linux-f26r:~/Projektid/progremise_infrastruktuur/andmevahetustarkvara/rakendusvõrgud/si
lktorrent/publitseerimishoidla/sandbox_of_the_Fossil_repository/wiki_references/2017/software/simulators/ns3_Discrete-event_Network_Simulator/doc$
fossil unversioned add
./2017_06_13_wget_copy_of_https_www_nsnam.org_documentation/bonnet/www.nsnam.org/docs/release/3.26/doxygen/structns3_1_1_ul_grant__s.html
''./2017_06_13_wget_copy_of_https_www_nsnam.org_documentation/bonnet/www.nsnam.org/docs/release/3.26/doxygen/structns3_1_1_ul_grant__s.html''
is not an acceptable filename
ts2@linux-f26r:~/Projektid/progremise_infrastruktuur/andmevahetustarkvara/rakendusvõrgud/si
lktorrent/publitseerimishoidla/sandbox_of_the_Fossil_repository/wiki_references/2017/software/simulators/ns3_Discrete-event_Network_Simulator/doc$
ls -l
./2017_06_13_wget_copy_of_https_www_nsnam.org_documentation/bonnet/www.nsnam.org/docs/release/3.26/doxygen/structns3_1_1_ul_grant__s.html
-rwxr-xr-x 1 ts2 users 17646 Apr 5 21:25
./2017_06_13_wget_copy_of_https_www_nsnam.org_documentation/bonnet/www.nsnam.org/docs/release/3.26/doxygen/structns3_1_1_ul_grant__s.html
ts2@linux-f26r:~/Projektid/progremise_infrastruktuur/andmevahetustarkvara/rakendusvõrgud/si
lktorrent/publitseerimishoidla/sandbox_of_the_Fossil_repository/wiki_references/2017/software/simulators/ns3_Discrete-event_Network_Simulator/doc$
---the-end-of-the-semi-irrelevant-citation----
I found one very old, year 2014 blog post, where
a person, who supposedly works on game development,
had problems with data imports that consisted
of a lot of small files. A citation from the
2014 blog post at
https://www.omiyagames.com/blog/2014/02/15/farewell-fossil-version-control/
(archival copy: https://archive.is/uBr3s )
--citation--start----
I use Unity, and I import a lot of things
from the Unity Asset Store. Importing things
from the asset store sadly proved to be a
gigantic problem for Fossil. See, Fossil is
not only terrible at dealing with large files
(like most distributed revision controls are),
but also terrible at dealing with very large commits.
--citation--end------
I do not exactly know, what he means by "importing from
the asset store", but I do know that games
have data items like images/sprites, 3D_models and
3D model analogues of "animated Gif files"(3D sprites),
sounds, game levels, etc. and those can be pretty huge.
I think that it might be pretty fun to know, whether the
Fossil can hold up to the demands of applied statisticians or,
the way they tend to call themselves nowadays, "data scientists".
Those loads from the various IoT swarms might be a huge
set of relatively small files, yet, to re-analyze the data
for verifying results the data used for scientific papers
should be versioned, so that independent parties can
check the calculations. Fossil would be PERFECT for
encapsulating both, the scientific paper, the exact
copies and versions of tools used for the scientific paper,
the tech notes and/or research log, as the wiki is also
versioned, and the exact data set that was used
for making the presented conclusions.
The reason, why I write the current letter
is that IF the insertion of large amounts of
very small files is still an issue, then
there would be an opportunity to fix it
before anybody reports the issue.
Thank You :-)
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
