On 9/23/05, nick vajberg <nickvajberg@yahoo.dk> wrote:
> I've seen this request quite a few times in the user
> list.
>
> The request is basically to allow "unversioning" a
> file. The only way currently is to copy the local
> version, then remove and commit. This is quite often
> undesireable, because you do not wish to delete other
> peoples version when they update. You just want to
> unversion it.
>
> Max Bowsher once suggested this syntax [1]:
> "svn rm --keep-in-wc"
>
> ...which I really like. The alternative, I guess, is
> another top-level function like "svn unversion
> <resource>", but that seems excessive.
>
> I work within a large organization where many people
> work on dev projects. It is quite frequest that
> user-specific project files (such as those from
> Eclipse or VS.NET) gets imported, or that someone adds
> and commit them at some point.
>
> In this case, --keep-in-wc would be excellent, to say
> the least.
Perhaps "svn obliterate" will solve this use case for you?
Perforce supports unversioning files but leaving them in the WC via
"p4 obliterate -y filename" (the -y option indicates "yes, I really
want to obliterate the file, and I know I can't ever get it back").
The "obliterate" feature deletes the entire history of a file, and
requires administrative privileges. Since "obliterate" tells Perforce
to "forget entirely" that a particular file ever existed, individual
clients maintain the same file in their WC, unversioned. It would be
great to see the same feature in Subversion (See Issue #516 for
details).
Cheers,
David
--
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 23 16:34:16 2005