[development] Managing node revisions with a backend like subversion?

Adrian Rossouw adrian at bryght.com
Sat Feb 25 03:39:58 UTC 2006

I've thought of this before, but I personally thought of it in the  
format of imports/ exports,
and generating a filesystem access mechanism for drupal, which could  
then entirely be stuck into
a repository.

The actions / workflows would help with this too, as you could  
trigger a commit every time a node
is changed.


On 25 Feb 2006, at 3:11 AM, Khalid B wrote:

> - This would force a dependancy on Subversion. What about shops
> who use CVS, others use bzr, ...etc.
not unless we develop a standard 'repository' module, kind of like we  
image instead of bmp, jpg etc modules.

Adrian Rossouw
Drupal developer and Bryght Guy
http://drupal.org | http://bryght.com

More information about the development mailing list