[EMAIL PROTECTED] (Larry Jones) writes:
> Jorge Godoy writes:
> >
> > I want something like that: I have an obsolete file, I "cvs rm" it and
> > commit my changes. When my development partner makes a "cvs up
> > -newflag" the file will be automatically removed from his machine.
>
> I still don't understand -- CVS already does that:
>
> (in one working directory)
> > bash-2.02$ cvs rm -f foo1
> > cvs remove: scheduling `foo1' for removal
> > cvs remove: use 'cvs commit' to remove this file permanently
> > bash-2.02$ cvs ci -mtest
> > cvs commit: Examining .
> > Removing foo1;
> > /public/CVS/foo/foo1,v <-- foo1
> > new revision: delete; previous revision: 1.5
> > done
>
> (in another working directory)
> > bash-2.02$ cvs up
> > cvs update: Updating .
> > cvs update: warning: foo1 is not (any longer) pertinent
> > cvs update: Updating bar
> > bash-2.02$ ls
> > CVS/ file with spaces foo3
> > bar/ foo2*
Shame on me...
I had a file where permissions were changed and the user wasn't able
to remove it (directory permissions changed by a mistake of him). I've
checked it here and it does work...
Sorry for not looking into it before (rule: don't trust that a user
has checked what he says he checked).
Thanks, Larry.
Sorry to all the others.
--
Godoy. <[EMAIL PROTECTED]>
Departamento de Publica��es
Publishing Department Conectiva S.A.
