Thread: Audit Trail
View Single Post
Old 03-20-2016, 10:35 PM   #8
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,848
Karma: 6120478
Join Date: Nov 2009
Device: many
The only way I think to achieve that is to combine some sort of revision storage with an automatic Sigil command logging function of some sort to provide the reason (culprit ) behind each change.

Even With a plugin and git/rcs/cvs system behind it, since these is no automatic sigil command logging, the user would still have to manually make a commit with a commit message explaining what commands caused the changes. So not what you want either.

Sorry.

KevinH
KevinH is offline   Reply With Quote