Thread: Audit Trail
View Single Post
Old 03-20-2016, 08:54 PM   #3
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,870
Karma: 6120478
Join Date: Nov 2009
Device: many
No Sigil is not a concurrent versioning system. Simple whitespace changes and xml order of attributes would be enough to overload most cvs systems with a sea of meaningless changes making what you want hard to find at best. Plugins changes would generate similar reams of meaningless changes.

So exactly what are you trying to track down and why? If reverting changes is important then I would place my epub unpacked into a revision tracker (cvs) and use plugins for import, output, and commit and let the version system track the changes. Just be willing to dig through simple whitespace and order of attribute nonsense when trying to find a specific change.

KevinH
KevinH is offline   Reply With Quote