On Fri, Jul 11, 2008 at 10:47:26AM -0400, Mark Phippard wrote:
> On Fri, Jul 11, 2008 at 10:41 AM, Rui, Guo <timmyguo_at_mail.ustc.edu.cn> wrote:
>
> > I'm just considering the behavior of 'svn remove' on sparse directory and find
> > something bad in it. I just demonstrate the problem first.
> >
> > svn co --depth empty http://server/greek_tree wc
> > cd wc
> > svn up --depth files A
> > svn rm A
> >
> > In this example, I have a partial copy of A directory in the greek tree. And
> > then I remove the directory A. After commit, the entire A tree will gone. This
> > seems nature at first. However, after a second thought, the remove operation
> > will affect more than user can see, which is quite dangerous. I know that
> > nothing is really unrecoverable in the circumstance of version management. But
> > I think it will not be a good user experience for the user to find out that
> > him did something bad just because subversion opened the dangerous door and
> > did not remind him.
>
> I personally do not agree this is a problem. If a user removes a
> directory, what other expectation would they possibly have?
He would probably just want to remove the files in that wc directory and
forget that there are many more hidden in the repository. This may happen if
he has been using the wc structure for a long time.
Rui
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-07-11 17:10:22 CEST