On Wed, May 7, 2014 at 10:32 AM, Andy Bradford <amb-fos...@bradfords.org>wrote:
> Thus said Richard Hipp on Wed, 07 May 2014 07:06:31 -0400: > > > The purpose of the hooks is to verify that all of the content in the > > repository is still accessible. Before each commit, the hooks run to > > verify that all of the artifacts can still be un-deltaed and > > uncompressed and they survive those operations intact. > > Hmm, that does indeed sound problematic to be disabled and it certainly > should not be done if it can compromise the integrity of the > artifacts. Perhaps I misunderstood the purpose of this block of code in > manifest_crosslink_end(): > > > http://www.fossil-scm.org/index.html/artifact/05e0e4bec391ca300d1a6fc30fc19c0a12454be1?ln=1506,1518 > We might be talking about different hooks. I'm concerned about the verify_before_commit hook implemented here: http://www.fossil-scm.org/fossil/artifact/615e25ed6?ln=94-104 -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
