Tossing old revisions for space reasons is already logged as an issue.
No need to do this the expensive way (reload the entire repository from
scratch) when we can just fix that separate issue on it's own, and in a
much more efficient way.
Bill
> -----Original Message-----
> From: David Mankin [mailto:mankin@ants.com]
> Sent: Wednesday, April 24, 2002 2:01 PM
> To: kfogel@collab.net
> Cc: SVN Dev List
> Subject: Re: fs dump/restore proposal
>
> On 24 Apr 2002, Karl Fogel wrote:
>
> > David Mankin <mankin@ants.com> writes:
> > > I'm not sure I fully understood the proposal, but what I think I'm
> picking
> > > up from the discussion is that the revision numbers (e.g. rev
1770)
> would
> > > not be maintained across a dump/restore. If I'm wrong, good.
Just
> let me
> > > know.
> >
> > Revision numbers will be preserved, worry not.
> >
>
> One of the discussed use-cases is one that also exists in CVS:
> svnadmin dump -r1000:HEAD | svnadmin create-and-load /newrepository
>
> (In CVS I think you have to do some tweaking of the ,v files to remove
> diffs, if I remember The CVS Book correctly.)
>
> I can see how this would be helpful for Subversion, but not if it
changed
> revision numbers. The most recent discussion sounds like revision
numbers
> wouldn't be restored in this situation, because the new repostitory
would
> have to start over at 1. Or maybe I'm still misunderstanding.
>
> -David Mankin
>
>
> ---------------------------------------------------------------------
> 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 Wed Apr 24 23:09:16 2002