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

Re: Howto freeze or archive a project

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: 2007-09-24 01:24:03 CEST

On Sep 23, 2007, at 17:13, Daniel Jimenez wrote:

>>> Any help suggestion on how to achieve this would be appreciated.
>> The structure you show at the end looks good to me. You could
>> use the word "Archive" (or "Archived") or "Old" or
>> "Deprecated" or "Obsolete"
>> or "Inactive" or anything like that. To move Project1 there,
>> you would:
>> svn mv url://to/SVNRep/Trunk/Project1 url://to/SVNRep/Archive
>> -m "Moving Project1 to the archive"
>> When anybody uses "svn update" in their working copy of the
>> entire Trunk, their copy of Project1 will be deleted (unless
>> they have local modifications, in which case those
>> modifications will be retained, though to commit them they'll
>> have to "svn switch" their working copy to the project's new
>> location in the archive).
> So far I am with you.
> However, say that at a later date, a developer needed to modify the
> "archived project1".
> (1) How would she/he do this, as it is not possible to check out
> the project
> to their local Project folder on their PC, as this folder already
> contains a
> .svn subfolder? This is where all development is currently occurring.

When you say "their local Project folder", do you mean a working copy
of Trunk or a working copy of Project1? If Trunk, then their Trunk
working copy no longer contains Project1, since Project1 has been
moved to the Archive which is outside of the Trunk. So the developer
needs to check out a new copy of Project1, to anywhere they like.
Then they work in that directory.

svn co url://to/SVNRep/Archive/Project1

Or, if the developer has an existing (possibly standalone) working
copy of Project1 from the old URL structure from which they want to
commit changes, they can switch the working copy to the new URL:

svn switch url://to/SVNRep/Archive/Project1 /existing/wc/of/Project1

> (2) If she/he does a manual checkout, How would she/he commit the
> changes?
> And to where ?

The developer would just make the changes as usual, and then issue
"svn commit" when desired. The working copy knows where in the
repository it's from, so nothing special needs to be specified.

Don't forget to Reply To All so that your reply goes to the mailing
list too, not just to me.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 24 01:26:04 2007

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.