Date: Sat, 14 Oct 2000 14:45:40 -0700 (PDT) From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Gerhard Sittig <Gerhard.Sittig@gmx.net> Cc: FreeBSD Current <freebsd-current@FreeBSD.ORG> Subject: Re: removing global from tree Message-ID: <200010142145.e9ELjeH15907@troutmask.apl.washington.edu> In-Reply-To: <20001014223211.T25237@speedy.gsinet> from Gerhard Sittig at "Oct 14, 2000 10:32:11 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Gerhard Sittig wrote: > On Sat, Oct 14, 2000 at 11:16 -0700, John Baldwin wrote: > > > > On 14-Oct-00 Gerhard Sittig wrote: > > > > > > Up to now I always thought "the Attic" is something CVS > > > itself takes care of when "cvs rm"ing files. What's that > > > special thing needing manual intervention or special > > > attention you've been talking about lately? Is it for > > > performance reasons or for the warm fuzzy feelings of having > > > "not too rotten a repo"? > > > > It is where CVS puts files when you cvs rm them. You just have > > to do the actual cvs rm/cvs ci. David was cautious because if > > he had to back the change out, he didn't want to have to try to > > cvs add all of the files back in. > > Isn't it true that all the "log", "diff", "up -r" and such > commands still work in the expected way? That's the reason for > having "the Attic", I thought. Not to remove the repo file when > the working file expires, but to keep the history and to restore > any previous revision thereof when requested. Backing out an > rm'ed file should be as difficult as doing the sequence I just > tested to make sure: > If I understands cvs docs, the problem isn't with individual files. Cvs doesn't handle the removal and restoration of directories very well. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200010142145.e9ELjeH15907>