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

RE: Re: after checked out an old revision...

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Thu, 13 Nov 2008 09:37:52 -0500

Couldn't you also delete the folder in the repository then do a Copy in
the repository of revision 95 to trunk. That will keep your history/log
just like revisions 96-101 never existed.

BOb

-----Original Message-----
From: news [mailto:news_at_ger.gmane.org] On Behalf Of Lorenz
Sent: Thursday, November 13, 2008 2:28 AM
To: users_at_subversion.tigris.org
Subject: Re: after checked out an old revision...

Steven Woody wrote:
>the head is 100, and i checked out an old revision, say 95, and
>finished many changes on the working copy. now, if i want to commit my
>working copy as revision 101 and do not take care anything from r95 to
>r100, what should i do?

depends how you want your history to look like.

With the methode Ryan describes, the changes and the fact that you
removed them again will show up in the log.

If you don't want the removed changes to show up in the log, you
alternatively can delete the folder in the repository (-> 101) and
reinstate it as a copy off of your working copy. That creates 102 as a
copy of 95 including your local changes.
If you want the copy to show up without modifications, you can first
do the copy in the repo (-> 102), switch you working copy to that
revision and then commit your changes (-> 103).

-- 
Lorenz
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-11-13 15:38:32 CET

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.