On Tue, Aug 12, 2014 at 1:35 PM, Stephan Beal <[email protected]> wrote:
> On Tue, Aug 12, 2014 at 10:29 AM, Baruch Burstein <[email protected]> > wrote: > >> I am curious how fossil itself manages this. While sqlite DBs (including >> the fossil repository) are generally expected to only be read/written with >> sqlite software (except for things like Dropbox), and thus only with >> "cooperating" programs, how does fossil lock files while it is committing >> them? I assume it must somehow keep a file from being changed while it is >> in the middle of a commit? >> > > For the most part, fossil only works with sqlite dbs, so it leaves the > locking/transactions to sqlite. It does not do any handling of locking of > non-db files (e.g. source files). > I was referring to the source files. Fossil doesn't lock them? Can't that cause problems with them getting changed in the middle of committing them? -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
