[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Any consequences over removing a subdir permanently?

From: S I
Subject: Re: Any consequences over removing a subdir permanently?
Date: Thu, 14 Jul 2005 13:12:43 -0700

Thanks for the input and all the helpful info.  I'm glad I posted :)

----Original Message Follows----
From: Todd Denniston <address@hidden>
To: S I <address@hidden>, address@hidden
Subject: Re: Any consequences over removing a subdir permanently?
Date: Thu, 14 Jul 2005 14:26:30 -0500
MIME-Version: 1.0
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.211); Thu, 14 Jul 2005 12:29:41 -0700 Received: from (address@hidden []) by with ESMTP id OAA27690; Thu, 14 Jul 2005 14:28:20 -0500
X-Message-Info: JGTYoYF78jHlrUEQ9SNZpCQAWdASPfyipP4Os14W2EY=
Organization: Code 6067, NSWC Crane
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.25glock1 i686)
X-Accept-Language: en
References: <address@hidden> <address@hidden>
Return-Path: address@hidden
X-OriginalArrivalTime: 14 Jul 2005 19:29:41.0641 (UTC) FILETIME=[61CA8F90:01C588AA]

Todd Denniston wrote:
Clerity demands I respond to my own post. sorry.

> S I wrote:
> >
> > We have restructured our code so many times and we may soon port over
> > to a completely clean repository without its history. So in our case it
> > shouldn't matter but I see your point about NOT exercising this.
> A middle ground might be:
> 1) tell everyone to commit all changes they have currently.
> 2) backup to cold storage media.
> 3) copy the CVS tree to a new location.
> 4) do a checkout from the new location and then do a `cvs watch on -R`
> against that checkout.
> 5) find and mark all the directories in the new copies location read only,
> and setup a lockdir for it so people can do readonly checkouts. (lock it
> down)
> 6) again backup to cold storage media.
 7) remove the unused directories, in the original (and still current)
version of the repo, i.e., no one has to change their CVSROOT values.

8) if people still have sand boxes from before there may be some difficulty
in doing updates and such, have them check that `cvs update -dP` command
works with out error at a minimum. If your really sure just have them remove
all their old sandboxes and start fresh.

> This should leave you with a copy in the new location for people who need to > know the ancient history, a copy to recover from if you hit enter on the rm
> in the wrong directory, and a smaller repo but with all the history since
> the each of the files were last restructured.

Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]