There has been lots of discussion about this over the years (https://www.google.ca/search?q=fossil-users+empty+directory).
I personally handle this (and other metadata things like user:group ownership or permissions (though we now handle --x (executable bit)) in a controlling file. Something like a purpose-built makefile or script that handles this layout, so that -it- can be versioned in fossil; fossil wasn't/isn't currently designed to handle that sort of metadata - which *arguably* should be handled in a script as described above. Fossil can then handle that script as an artifact. -bch On 8/1/16, Adam Jensen <han...@riseup.net> wrote: > Hi, > > I haven't before used fossil to manage a project. Is there a way to > commit empty directories to the repository so the project's directory > structure can be preserved and reconstructed? > > Actually, some of the directories aren't empty but rather their contents > are ignored: > > fsl add --ignore '*.db,*.fossil,*.log,*.mp3' * > fsl commit -m "Initial checkin" > > Is this something simple that I haven't yet discovered in the > documentation or am I doing something terribly wrong? > > Thanks! > _______________________________________________ > 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
