I know Fossil is a *file* versioning system, but when first establishing a repository for a working group, it is useful to create a straw-man folder structure to guide growth. But, one can't (by default?) commit an empty folder to a fossil repository, as there's nothing to 'version'.
For example, when developing games with UDK, they recommend a folder structure like this: ├───official_game_assets │ ├───alpha │ ├───beta │ │ ├───Binaries │ │ ├───Development │ │ ├───Engine │ │ │ ├───Config │ │ │ ├───Content │ │ │ │ ├───Functions │ │ │ │ └───Maps │ │ │ │ └───Template │ │ │ ├───Extras │ │ │ ├───Localization │ │ │ ├───Shaders │ │ │ └───Stats │ │ └───UDKGame │ │ ├───Autosaves │ │ ├───Build │ │ ├───Config │ │ ├───Content │ │ │ ├───Maps │ │ │ ├───Mobile │ │ │ ├───Private │ │ │ ├───Shared │ │ │ ├───Showcases │ │ │ └───TestPackages │ │ ├───Flash │ │ ├───Localization │ │ ├───Logs │ │ ├───Movies │ │ ├───Scripts │ │ └───Splash Is there a way around this? Can you commit an empty folder somehow? (I'd prefer to not have to go generate a placeholder "readme.txt" or ".purpose" file for each folder, just to get Fossil to recognize that it should exist... but I will if i must.) Just curious... -jer
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
