Re: Dropping Subversion

> > To protect a developer from accidental checkout of all the tags
> > and branches, subversion repo must be organized so tags
> > constitute separate tree. And then we get to the problem of
> > inefficient huge tags&branches bag which can not be easily
> > navigated to from the working copy.
>
> This is FUD. I use this directory structure on my own repo. Worst case
> scenario I don't realize my mistaken and I wait. Standard scenario, I
> hit cancel.

... and spend some nice time removing unnecessarily checked out files

> In pratice, I haven't really had this problem. I did it
> once when I first set up the repo. Haven't since then.

How do you check out next fresh working copy? Do you check out each
module separately? What about updating?

> You can't possibly be seriously suggesting that the versioning system
> should stop someone from doing something just because it might be stupid
> in some particular cases?

I think that such type of discussion does not lead to anything useful.

> Besides checking out all of the tags could
> potentially be a valid thing to do if you wanted to reoganize the repo
> in a single commit (though there are other ways to do that too).

Maybe. But seems to me, it would be more natural NOT to checkout all the
tags by default and give -I_know_what_I_am_doing switch for those rare
cases where someone really wants to do that.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 3 01:51:12 2004