Re: Encapsulating internal diffs?

On 17/05/2007 23.49, H. S. Teoh wrote:

> Any suggestions as to how to improve this? The CM process is
> unfortunately unlikely to change---they still want us to submit diffs
> rather than have direct commit access.

Well, depends on what you mean by "commit access".

Instead of a diff, each developer could create a new branch from trunk and
does his/her modification in it. When the patch is ready, he just sends an
e-mail to the CM, who just needs to checkout/switch/log the branch and decides
if it's good or not. If it's ok, he can merge it to trunk with one simple
command (including all the history-sensitive changes).

Otherwise, have a look at "svk", who has a way to manage a local patch queue
for each user, and submit patches with full history information which are even
machine-parsable.

-- 
Giovanni Bajo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org