Re: On using svn for submitting patches

Marc Singer wrote:

> My first approximation is to let the trunk reflect the published
> development process with a branch for each line of development. For
> example, a bug fix would be pursued on a branch of its own. Likewise,
> new features are developed in a branch per submittable chunk.

To pile on to the other responses, yes, this is exactly the way to do it. I
have been working on several major enhancements to Perl (dealing with version
objects). Perl is currently managed in Perforce, so I have a custom repository
of Perl (using the amazing apc2svn) in subversion.

I create a branch (or several) for my development work, to which I merge from
the trunk occasionally. When I am ready to submit a patch, I make sure I merge
from the trunk one last time (to test that the patch is not going to break
anything), then I do a diff from the HEAD of the branch to the HEAD of the
trunk, and this is what should apply.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org