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

Re: FAQ entry needs improvement

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 27 Sep 2011 21:57:28 +0300

Ulrich Eckhardt wrote on Tue, Sep 27, 2011 at 11:57:42 +0200:
> Am 26.09.2011 23:42, schrieb Ryan Schmidt:
> >On Sep 26, 2011, at 05:20, Daniel Shahaf wrote:
> >
> >>https://svn.apache.org/repos/asf/subversion/site/publish/faq.html#undo
> >>
> >>It's the most frequently asked question on IRC, and I'm tried of
> >>invoking the 'undo' factoid, perhaps people can help patch that entry to
> >>make it clearer?
> >>
> >>Thanks.
> >>
> >>
> >>< wayita> undo is done using 'svn merge' or 'svn copy':
> >> http://svnbook.red-bean.com/nightly/en/svn.branchmerge.basicmerging.html#svn.branchmerge.basicmerging.undo
> >
> >What would make the FAQ entry clearer?
>
>
> The FAQ entry mentions merging or copying, while the referenced
> entry in the documentation only explains merging.
>
> I just tried to write how to use "svn copy" to bring an old revision
> to the top, but I actually can't do that from my head. I know that I
> can delete the current head and then copy the old version to the
> same location using revisions while using repo URLs. I can imagine
> the same in a single commit using a working copy. Both should be
> easy for any SVN user.
>
> What I'm not sure is how that would work if I tried to copy a
> directory on top of another directory, i.e. if the directory
> wouldn't be copied into the other directory instead. Since it's hard
> to undo revisions, I'd wish for the FAQ to give me a recipe for that
> or tell me it's impossible.
>

In 1.7 you can do such directory replacements in the working copy.

You can always do:

svnmucc -m "The trunk is dead, long live the trunk!" rm $URL/trunk cp HEAD $URL/branches/foo $URL/trunk
Received on 2011-09-27 20:58:11 CEST

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.