[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Tool support for proposal/approval/commit process?

From: Andrew Thompson <subversionuser_at_aktzero.com>
Date: 2005-05-09 16:26:21 CEST

Schmitt, Michael wrote:
> Hello,
> in many open source projects, it is a good tradition to send a patch to
> the developer's mailing list first and wait for approval by a second
> developer, before the patch is actually committted.

I was toying with this idea. I had also considered having a tool accept
a patch, copy the trunk(or the user-designated base) to a new branch and
apply the patch there. Then, anyone wanting to test the patch could
switch a WC to that branch.

The patch could be tweaked (with version control) and once accepted
could be merged back into it's base(trunk). (I can definately see where
native distributed development support could be useful.)

One problem I thought of was that moves/adds/deletes can't be
represented as diffs, so they couldn't be handled in the original bug
opening. I guess one could submit a ticket without any changes, then
commit your moves/adds/changes/patches to your new ticket branch.

Just thinking out loud...

Andrew Thompson
Interested in a hosted SVN repository? Email me, let's talk...
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 9 16:31:11 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.