Now I'm confused. How is it a feature?
Assume that I want to be able to say "This is the newest source code
from the vendor. This file foo.m is now gone, and not used. No changes
have been made to foo.m on my system; it is still version 1.1.1.1; it is
not used anymore. I want it to disapear from future checkouts". How do I
do that?
And, if foo.m is at 1.2, and the new import of 1.1.1.2 is a removal,
what would it take to get it marked as a conflict, with the new version
being empty (in other words, showing the merge/conflict file as only
having my modifications, so I can move the added routines to another
file where they (now) properly belong)?
"Greg A. Woods" wrote:
>
> [ On Tuesday, May 9, 2000 at 21:43:26 (-0700), Tom Tromey wrote: ]
> > Subject: Re: bug in import?
> >
> > Michael> There appears to be a bug in import. It looks as though a
> > Michael> second import that does NOT have a file that was present in
> > Michael> the first import will not result in that file being dead.
> >
> > This is a known limitation of cvs import.
>
> Can you spell F E A T U R E ? :-)
>
> This is how automated file removal is handled. Not marking the "newly
> missing" file as "dead" (removed) was a long long long standing bug.
What do you mean by "automated file removal"?
Greg A. Woods
>
> +1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <robohack!woods>
> Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
(Incidently, I get bounces anytime I try to send to [EMAIL PROTECTED])
