Suggestions

[TK Soh]

--- Thomas Arendsen Hein <thomas at intevation.de> wrote:

> * TK Soh <teekaysoh at yahoo.com> [20050809 05:51]:
> > > Second suggestion:
> > > 
> > >     I've always been frustrated by the behavior of "remove" in cvs
> > >     that forces you to first remove the file before you can actually
> > >     call cvs remove on it. It turns out that hg seems to be behaving
> > >     the same. Is there any chance of having hg being less anal about
> > >    this and letting the user do an hg remove on a file even though it
> still
> > >     exists in the directory ?
> > 
> > I was griping about this awhile ago. It turns out there's really no need of
> hg
> > remove, simply deleting the files seemed to be enough:
> > 
> >     % rm sub/sub2.c
> >     % hg status
> >     R sub/sub2.c
> 
> This is a bug and will be fixed soon :)
> 
> Of course a --force flag to 'hg remove' would be good here.

Just make sure the option is there before you fix the bug ;-) BTW, while you
are at it, can you look at this also?

    % hg rm sub/sub2.c
    % hg status
    R sub/sub2.c
    % hg revert
    % hg status
    ? sub/sub2.c

Looks like Hg somehow forgot about sub/sub2.c after doing rm.


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com