I don't think a fixed number of revisions is as useful as a date cutoff. If someone uses revisions so community members can edit nodes, it's very easy to abuse a fixed number per node cutoff. Greg Holsclaw wrote:
http://drupal.org/project/revision_deletion is probably a long way from ideally suited for this, as it trims by age of revision, not the number of revisions, but it may be a decent starting point.
-Greg
-----Original Message----- From: development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Larry Garfield Sent: Thursday, June 07, 2007 11:17 AM To: development@drupal.org Subject: Re: [development] Requiring node revisions
There are cases where I don't want revisions at all. Maybe I don't want a paper-trail. :-)
If the code is considerably simpler if revisions are required, then I would say we should also consider it a requirement that we have auto-trimming of revisions in core, per node type, (only keep the last X revisions of node type Y), and document that setting it to 0 will have "no revisions saved". That becomes the new alternative way of saying "revisions off", but has cleaner code.
--Larry Garfield