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

Re: Adding changeset-like functionality to subversion

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-10-11 19:53:43 CEST

"LOWE,DAVID (HP-Vancouver,ex1)" <dave.lowe@hp.com> writes:

>
> There is also the problem of change removal, which has not been talked about
> much. As I understand it , to remove a change you must, first of all, have
> committed right after the merge. Then, assuming the commit created rev N,
> you can back out that change by cloning rev N-1 and merging revs N+1:Head.
> All of which is a bit cumbersome.

It's not that complex.

There's no need to clone rev N-1. It already exists. Instead, you
make your *working copy* look exactly like rev N-1, and then commit.

That is, apply changeset N in reverse to your working copy:

    svn merge -r N:N-1 URI working-copy
    svn commit

Now revision N+1 and N-1 look identical in the repository.

This procedure can be used remove *any* changeset from repository
HEAD, not just the latest changset to have been committed.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 11 19:55:42 2002

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.