On Tuesday 12 April 2005 15:18, Nicolás Lichtmaier wrote:
> >>Please read over
> >>
> >> http://subversion.tigris.org/issues/show_bug.cgi?id=516
> >>
> >>to see the complexities of 'obliterate', and why we haven't
> >>gotten around to it yet. It's not impossible to implement,
> >>but some specification work is needed first.
> >
> >Understood. I just thought I'd provide a real world example of why
> >obliterate would be incredibly useful.
>
> You "real world example" is invalid. Storing executables/build results
> in a *source* control system is wrong. Use a network share for that.
I'd hardly call it "invalid". Questionable, maybe, but certainly not
invalid. In support of military missions, we regularly check in binaries
for equipment that's sent to the field, along with any necessary
debugging symbols. They've came very much in handy when the environment
has changed a little (i.e., build utilities have been upgraded), and what
you build is no longer equal to what's been shipped. Having the binaries
stored off has enabled us to go and conduct a few post-mortem activities
that would have otherwise been impossible. And, having those right there
in Subversion is *extremely* handy.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 13 01:01:27 2005