Re: Any consequences over removing a subdir permanently?

[S I]

Thank you as always.

Do you think though that deleting a dir and later retrieving a dead file 
would confuse the dead file where to implant itself?  I have a dummy 
repository and I'm going to try this to find out the outcome.

The subdirs I speak of are about 5 years old and don't think anyone would 
care.  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.

Thanks. :)

----Original Message Follows----
From: Todd Denniston <[EMAIL PROTECTED]>
To: S I <[EMAIL PROTECTED]>
CC: info-cvs@gnu.org
Subject: Re: Any consequences over removing a subdir permanently?
Date: Thu, 14 Jul 2005 12:13:32 -0500
MIME-Version: 1.0
Received: from mail.ssa.crane.navy.mil ([164.227.42.3]) by 
mc7-f2.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 14 Jul 2005 
10:13:35 -0700
Received: from ssa.crane.navy.mil ([EMAIL PROTECTED] 
[164.227.42.142]) by mail.ssa.crane.navy.mil  with ESMTP id MAA27385; Thu, 
14 Jul 2005 12:15:22 -0500
X-Message-Info: JGTYoYF78jEHjJx36Oi8+Z3TmmkSEdPtfpLB7P/ybN8=
Organization: Code 6067, NSWC Crane
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.25glock1 i686)
X-Accept-Language: en
References: <[EMAIL PROTECTED]>
Return-Path: [EMAIL PROTECTED]
X-OriginalArrivalTime: 14 Jul 2005 17:13:35.0856 (UTC) 
FILETIME=[5E9AA700:01C58897]

S I wrote:
>
> Hi
>
> I know how to delete and commit files to the attic and on the next 
checkout
> do a -P to prune out empty dirs but I have not seen any documentation on 
how
> to remove empty dirs/subdirs permanently.  Is this not recommended lest 
you
> have to retrieve dead files later? And CVS wouldn't know what structure 
to
> retrieve them to?  Should I or not delete the empty dirs on the server 
side
> or too dangerous?  We have many, and I mean many, empty dirs just sitting
> there!

Deleting anything permanently out of a version control system is _usually_ a
_very_ BAD idea. However if your project management really desires it, keep
your self sane with a good backup, and go directly into the repository and
`rm -fr  offensive_directory_structure`. The reason that cvs does not have a
built-in command (that I am aware of) for doing this is that it is such a
_very_ BAD idea.


Got permission and a backup?
Happy hunting. :)

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




_______________________________________________
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs