[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Best way to "un-version control" a file?

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Thu, 23 Sep 2010 12:27:40 -0500

On 9/23/2010 12:00 PM, Daniel Shahaf wrote:
> Les Mikesell wrote on Thu, Sep 23, 2010 at 09:29:31 -0500:
>> And if it isn't for subversion, it is likely only because the request
>> has been ignored and put off for so long that everything thinks it is
>> hopeless to ask again.
>
> In other words: regardless of what people actually say and do, you're going
> to tell us that that feature is #1 on their wishlist. I don't buy this logic.

Believe what you want. I know our repository has clear-text passwords
embedded in scripts that shouldn't have been committed, and also some
large binaries that don't belong. The password business is particularly
bad because we have fisheye doing full-text indexing of all the
revisions which makes them easy to find even when deleted out of recent
versions.

Am I wrong in thinking that similar accidents happen to everyone
eventually and that a feature to fix them would be desirable? There
would actually be two flavors of obliterate that would be useful. One
that simply made specific revs permanently unreadable and another that
frees the space.

-- 
   Les Mikesell
    lesmikesell_at_gmail.com
Received on 2010-09-23 19:28:41 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.