You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Justin Hahn <je...@Isomorphic.net> on 2003/01/07 05:44:52 UTC
Looking for the equivalent of p4 obliterate...
I'm a long time perforce user (some of you may be familiar with it,
others not...) I've been playing with subversion lately, and generally
my experience has been VERY positive. So far, for the most part, it
looks like you've taken the best aspects of perforce, CVS and bitkeeper
and melded them into a really nice SCM. (I'm very nearly a convert...)
However, I've yet to figure out how to completely, and truly, delete
something from a repository. I know, I know, this is a bad idea. But
every now and again someone goes and does something so truly and
absolutely brain-dead you don't even want it in the repository. (or
then, sometimes, there are political reasons... Telling the VP of
Development that you can't permanently remove some files, no matter how
bad an idea it is doesn't always fly...)
Perforce has a very handy way of doing this: the "obliterate" command
(which requires admin access to the repository, and a bunch of other
safeguards.) Is there an equivalent function in svnadmin or the svn?
While I can probably live without it, this functionality has been quite
valuable on a couple occasions. (You checked in how many gigs? Why the
hell? etc.) Even with CVS, if you really new what you were doing, you
could pull this off with rm and some editing.
The only thing I could find in the archives was a short thread from
about a year ago suggesting this was to be implemented.
--jeh (please cc me, I'm not on the list..)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Looking for the equivalent of p4 obliterate...
Posted by Branko Čibej <br...@xbc.nu>.
Garrett Rooney wrote:
> Justin Hahn wrote:
>
>> Perforce has a very handy way of doing this: the "obliterate" command
>> (which requires admin access to the repository, and a bunch of other
>> safeguards.) Is there an equivalent function in svnadmin or the svn?
>> While I can probably live without it, this functionality has been
>> quite valuable on a couple occasions. (You checked in how many gigs?
>> Why the hell? etc.) Even with CVS, if you really new what you were
>> doing, you could pull this off with rm and some editing.
>>
>> The only thing I could find in the archives was a short thread from
>> about a year ago suggesting this was to be implemented.
>
>
>
> well, nobody's saying that we shouldn't have this feature, but due to
> the fact that the file system is designed specifically /not/ to ever
> lose data, it's not exactly a simple change. what you're asking for
> will most likely be implemented post 1.0 as a result.
It is, in fact, planned for after 1.0; see
http://subversion.tigris.org/issues/show_bug.cgi?id=516.
> that said, if you're willing to get intimately familiar with our dump
> format, you could likely manage to dump the repository, restore
> everything from before the stuff you don't want went in, then
> selectively add in revisions after that point excluding the parts that
> involve the stuff you're trying to get rid of. i'm not positive this
> would work, but i suspect it would, although it would likely not be
> much fun to do.
The easiest way would be to just edit the dump file, removing all
references to the "obliterated" data. It's not exactly the easiest thing
in the world, but it should be possible, but note the warnings in the issue.
--
Brane Čibej <br...@xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Looking for the equivalent of p4 obliterate...
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
Karl Fogel wrote:
>Garrett Rooney <ro...@electricjellyfish.net> writes:
>
>
>>well, nobody's saying that we shouldn't have this feature, but due to
>>the fact that the file system is designed specifically /not/ to ever
>>lose data, it's not exactly a simple change. what you're asking for
>>will most likely be implemented post 1.0 as a result.
>>
>>
>
>Yes. We're even planning to call it "obliterate", I believe :-).
>
>
of course we are, that name is just too cool not to steal ;-)
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Looking for the equivalent of p4 obliterate...
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Garrett Rooney <ro...@electricjellyfish.net> writes:
> well, nobody's saying that we shouldn't have this feature, but due to
> the fact that the file system is designed specifically /not/ to ever
> lose data, it's not exactly a simple change. what you're asking for
> will most likely be implemented post 1.0 as a result.
Yes. We're even planning to call it "obliterate", I believe :-).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Looking for the equivalent of p4 obliterate...
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
Justin Hahn wrote:
> Perforce has a very handy way of doing this: the "obliterate" command
> (which requires admin access to the repository, and a bunch of other
> safeguards.) Is there an equivalent function in svnadmin or the svn?
> While I can probably live without it, this functionality has been
> quite valuable on a couple occasions. (You checked in how many gigs?
> Why the hell? etc.) Even with CVS, if you really new what you were
> doing, you could pull this off with rm and some editing.
>
> The only thing I could find in the archives was a short thread from
> about a year ago suggesting this was to be implemented.
well, nobody's saying that we shouldn't have this feature, but due to
the fact that the file system is designed specifically /not/ to ever
lose data, it's not exactly a simple change. what you're asking for
will most likely be implemented post 1.0 as a result.
that said, if you're willing to get intimately familiar with our dump
format, you could likely manage to dump the repository, restore
everything from before the stuff you don't want went in, then
selectively add in revisions after that point excluding the parts that
involve the stuff you're trying to get rid of. i'm not positive this
would work, but i suspect it would, although it would likely not be much
fun to do.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Looking for the equivalent of p4 obliterate...
Posted by Ben Collins-Sussman <su...@collab.net>.
Justin Hahn <je...@Isomorphic.net> writes:
> However, I've yet to figure out how to completely, and truly, delete
> something from a repository.
'svn obliterate' has been a feature request in our issue tracker for a
very long time. See issue #516. It's scheduled as a post-1.0 feature
for now.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Looking for the equivalent of p4 obliterate...
Posted by Peter Davis <pe...@pdavis.cx>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 06 January 2003 21:44, Justin Hahn wrote:
> --jeh (please cc me, I'm not on the list..)
I think it's pretty common practice around here to CC people even if they
are on the list, but for future reference, check out
http://www.gmane.org/
and, following the links,
news://news.gmane.org/gmane.comp.version-control.subversion.devel
I've found it pretty handy when I'm away from my normal email.
- --
Peter Davis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+GtiThDAgUT1yirARAtAuAJ0b0TYL5Cy2I09d8qIbwBpjUBjJogCghwp+
AEEcCHXcSL/9AaFyjztGegk=
=ASx2
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org