Hello, Svn suffers from other issues, and AFAIK the it will not allow commits to other from one person to be applied by another. So in the situation of drupal where we have a few lieutenants that commit patches to core, the commits are marked as coming from them, and not the original person. If you take a distributed source management system like bitkeeper, arch, bazaar, git and others you can have the lieutenants commit the patch to the core, by getting the change set from the original developer's repository or via other means and the history, comments and user data is retained. Gordon. -----Original Message----- From: drupal-devel-bounces@drupal.org [mailto:drupal-devel-bounces@drupal.org] On Behalf Of Adrian Rossouw Sent: Thursday, 5 May 2005 9:47 AM To: drupal-devel@drupal.org Subject: Re: [drupal-devel] PHPTemplate hits core ... finally -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05 May 2005, at 1:35 AM, Gordon Heydon wrote:
<cvs rant>
Darix has showed me some nifty SVN things, and convinced me that we should move Drupal to svn. - -- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFCeV79gegMqdGlkasRAphZAKDWjeuxPnebP0vS+8Y/8q6HTUEjoQCgz80Q 4KIKCky6W1CBxqAwxWZcxDs= =GyD2 -----END PGP SIGNATURE----- !DSPAM:4279601e72505005216706!