How will a client act if one of its current files is obliterated?
-David Waite
On Thu, 05 Aug 2004 15:12:09 -0700, Justin Erenkrantz
<justin@erenkrantz.com> wrote:
> --On Thursday, August 5, 2004 3:07 PM -0500 "C. Michael Pilato"
> <cmpilato@collab.net> wrote:
>
> > So, I must confess that I was not completely upfront in my reply.
>
> Heh.
>
> > I don't have a script which does the work needed to say, remove
> > evidence of a file's content ever being present in a repository. But
> > I *do* have a script (begun some time ago, but never finished) which
> > simply unlinks all revisions of a file from their parent directories.
> > I never donated said script because it was guaranteed to break
> > repositories in a particular way (doesn't munge the all-important
> > 'changes' table).
>
> Is the changes table schema documented? With your script, what is broken?
>
> > But it's kinda silly to allow you guys to begin work from scratch on a
> > tool that delves deeply into a knowledge domain in which I am quite
> > strong when, I believe, the lion's share of the work has already been
> > done. So while I don't have time to take this script to completion,
> > hopefully you can pick up where I left off.
> >
> > Hit me with questions if you need to.
>
> Like 'where's the script?' ;-) -- justin
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 6 00:15:34 2004