Sounds like a winning suggestion. Having issues with it though. specifying \developer\jer results in: c:\fossil\fossil.exe: couldn't create directory \developer\jer as required by empty-dirs setting
specifying /developer/jer results in: c:\fossil\fossil.exe: couldn't create directory /developer/jer as required by empty-dirs setting specifying developer/jer results in: c:\fossil\fossil.exe: couldn't create directory developer/jer as required by empty-dirs setting Any ideas? On Tue, Mar 20, 2012 at 8:51 AM, Benoit Mortgat <mort...@gmail.com> wrote: > On Tue, Mar 20, 2012 at 16:28, Jeremy Anderson <jere...@gmail.com> wrote: > > 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 > > You can use the versionable setting “empty-dirs”. Create a file named > .fossil-settings/empty-dirs in your checkout, and fill it with: > > /official_game_assets/alpha > /official_game_assets/beta/Binaries > ... > > Add that file to the fossil repository, this will maintain a versionable > list of empty directories. > > > -- > Benoit Mortgat > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
