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

Re: On using svn for submitting patches

From: <kfogel_at_collab.net>
Date: 2003-10-10 04:41:03 CEST

Marc Singer <elf@buici.com> writes:
> 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.
> The questions are
> Is this a reasonable method for developing 'patches'?
> Is there something better?

I'm not sure what you concretely mean by "developing 'patches'", but
this is a reasonable way to handle multiple related lines of
development. When a bug is fixed on one line, and is known to apply
to others too, use 'svn merge' to port it across. Try to keep
experimental branches short-lived: when the experiment is done, merge
the changes into some more permanent line and remove the branch.

That's my $0.02, YMMV :-).


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 10 05:15:53 2003

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

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