[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: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-10-10 18:29:14 CEST

Marc Singer <elf@buici.com> writes:

> Now, I realize that I made an error in patch_1 and I'd like the change
> to propagate without affecting the contents of patch_2 which remains a
> single line change.

"Propogate"? What does that mean?

In subversion, patches are not first-class objects; trees are. You
have a branch-tree which represents the results of a long line of
changes. But there's no way to talk about cause and effect: "hey, I
want to change patch 1, which therefore has a ripple effect on
subsequent patches." There are no 'patch objects' to manage.
Instead, you just keep making changes to your branch, so that the
*result* (i.e. HEAD tree on your branch) looks as *if* patch 1 had
been changed way back in time.

It sounds to me like you're talking about the arbitrary composition of
patches, where each patch ("changeset") exists as an 1st-class object
with its own life. You want to build arbitrary trees by composing
arbitrary patches; the trees are the derived objects.

It sounds like you want 'arch'. :-)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 10 18:31:34 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.