Re: subversion vs cvs (Was: Re: linked list rewrite) - Mailing list pgsql-hackers

From Dustin Sallings
Subject Re: subversion vs cvs (Was: Re: linked list rewrite)
Date
Msg-id BDA431A7-7E97-11D8-9C78-000393CFE6B8@spy.net
Whole thread Raw
In response to Re: subversion vs cvs (Was: Re: linked list rewrite)  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-hackers
On Mar 25, 2004, at 5:05, Jan Wieck wrote:

> The difference here is that instead of submitting a patch for review, 
> which is then frozen, the branch owner can (and that means some will, 
> no matter what your intentions are) keep modifying the branch during 
> the review process, other than just keeping it in sync with 
> conflicting changes to the trunk. How do you plan to prevent that?
You do both.  Changesets are immutable.  A patch cannot be modified.  
However, new patches can be added for tracking changes to the tree.  
You can review the original diff, and you can review how it's tracked 
head-of-line changes independently.  You can take the original diff and 
manually wedge it in if you want, or you can see how the latest 
progress differs before submission.

-- 
Dustin Sallings



pgsql-hackers by date:

Previous
From: Dustin Sallings
Date:
Subject: Re: subversion vs cvs (Was: Re: linked list rewrite)
Next
From: Dustin Sallings
Date:
Subject: Re: subversion vs cvs (Was: Re: linked list rewrite)