A question related to my last post is how it may be possible to use / abuse fossil for elements which are essentially not file based - that is because the artefacts are in the db, rather than tied to files.
In my case I'd like to be able to keep track of script elements, handlers, functions, methods, classes etc and not the files they happen to be in. So a function in one script and a function in another would be the same artefact in the db, even if they were in different script files. I'm not sure if this is a real difference, as with GIT I was going to have to split these out into seperate text files, and being stored in a db is much the same, but I am wandering how I can use the db to store metadata such as the files the function is found in, so that I can link the script elements to these files.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users