IIRC VSS gives 'obliterate' rights to general users (in true Microsoft form),
doesn't it? That being the case, wouldn't restricting obliterate to admins help
curb the problem? Namely, that allowing regular users to obliterate empowers
them to inattentively check in ...let's call it "problematic stuff"..., and, as
a result, obliterate too often, which in turn wrecks meaningful pieces of the
repository?
Did I get that right?
Peace,
Michael A. Smith,
Web Designer
michael.smith@lanxess.com
LANXESS Corporation
111 RIDC Park West Drive
Pittsburgh, PA 15275-1112
(412) 809 1518
|---------+---------------------------->
| | "Brian Jackson" |
| | <Brian.Jackson@ze|
| | dak.com> |
| | |
| | 04/18/2005 02:16 |
| | PM |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------------------------------------|
| |
| To: "'Subversion Users'" <users@subversion.tigris.org> |
| cc: |
| Subject: RE: Another request for obliterate... |
>------------------------------------------------------------------------------------------------------------------------------------------------------------|
Scott,
Having just recently migrated from VSS to SVN I can testify to the
opposite. The VSS 'obliterate' equivalent ('Destroy permanently') would
break all previous labels (VSS equivalent of tags) of a project. We would
be unable to get a copy of a label if that label contained a file that had
been 'obliterated'. I would second Tim's experience that 'obliterate' has
unintended side-effects.
Brian
-----Original Message-----
From: Scott Palmer [mailto:scott.palmer@2connected.org]
Sent: Monday, April 18, 2005 1:56 PM
To: Subversion Users
Subject: Re: Another request for obliterate...
On Apr 18, 2005, at 1:27 PM, Tim Hill wrote:
> OK, I agree that production disk costs are more significant. However,
> I think the cost of an obliterate command would be higher. Why?
> Experience! I've worked on large projects where the SCC system did
> have such a feature -- and what a mess it caused. First, people would
> not think before a check-in ("I can always obliterate it later"), so
> in fact *more* junk was checked in than ever (now start thinking disk
> costs). Second, every single obliterate caused horrible shock-waves. I
> would get people to swear on their mother's graves that the obliterate
> would have no side-effects and it *always* did. Builds broke. Diffs
> went into the left field. Yuck.
>
> Now, this was a large project, pretty well managed, and not in any way
> atypical.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 18 20:57:59 2005