I'm testing out Fossil for a small project that needs source control and a bug tracker. It looks quite nice except that I can't quite figure out two things that I need to accomplish. Please excuse me if I don't quite have all of the terminology correct yet.
My Fossil repository is structured as a series of directories that contain scripts, fonts, XML files, and proprietary Geographic Information System (GIS) databases. 1) A single commit may involve multiple files. I haven't been able to figure out how to easily rollback a single file from a specific commit. Scenario: We edit a file (File A) multiple times over a week, committing each major change, say once a day. The daily commit may involve other file with other, unrelated changes. We realize that some other aspect of File A corrupted at some point over that week and wish to rollback just File A to the beginning of the week, but retain all changes to other files that were committed during the week. I've gone back and downloaded the old file into the local working directory, then re-committed it. Is this the expected, recommended way of rolling back that one file? 2) We store GIS databases, specifically Esri File Geodatabases. These appear in the file system as a directory containing multiple files. The files are all binary. The directory of files acts in its native software as a single database. A single edit to the Geodatabase can result in multiple files being altered and potentially files added or removed. Fossil seems to detect all of these changes just fine. My problem is more about how to roll back such a directory. How can you roll back an entire directory at once, without having to go get individual files? (there could potentially be hundreds of files...) Thanks for the help. stongey
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
