From: Steve W. <sw...@wc...> - 2000-07-15 18:08:02
|
On Sat, 15 Jul 2000, Jeff Dairiki wrote: > On what to archive: > I think we all agree that we don't want to archive everything. The > question is how to filter out the small edits. > > When the author changes we should force the old version to be archived. > This keeps competing authors from wiping each others work. I agree... author change == "commit" > So the question remains what to do when an author is editing his own work: > > Personally, there have been many times I've checked something into CVS > (or some other version control system) when I've almost immediately > discovered some braino and wanted to erase the checkin. > > I envision a check-box on the edit form labelled something like > "This is a minor edit. Do not archive previous version." The default > state of this button could be made to depend on the time since the > last edit (if it's been awhile, the default would be to make a backup). > > To me it seems better to decide at edit time whether a change is "minor", > than to try to guess whether the next change will be "minor". > > I suppose this is not incompatible with another checkbox labelled "commit", > which would set a PRECIOUS bit in $pagehash['flags']. Doable; I would be happy with a "commit" button, but people would probably just commit every change they make... hmm... maybe store whole versions when authors change, and diffs when an author edits their own work? Just a thought. > Cool idea which just popped into head: > > Once the version history stuff is in place, must add 'diffs' link to > RecentChanges entries. > I am drooling... :-) sw ...............................ooo0000ooo................................. Hear FM quality freeform radio through the Internet: http://wcsb.org/ home page: www.wcsb.org/~swain |