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

RE: Breaking-up Large Repository

From: Giulio Troccoli <giulio.troccoli_at_uk.linedata.com>
Date: Thu, 16 Jul 2009 11:19:29 +0100

>

Linedata Services (UK) Ltd
Registered Office: Bishopsgate Court, 4-12 Norton Folgate, London, E1 6DB
Registered in England and Wales No 3027851 VAT Reg No 778499447

-----Original Message-----

> From: Ryan Schmidt [mailto:subversion-2009b_at_ryandesign.com]
> Sent: 16 July 2009 01:09
> To: Giulio Troccoli
> Cc: users_at_subversion.tigris.org
> Subject: Re: Breaking-up Large Repository
>
> On Jul 15, 2009, at 03:58, Giulio Troccoli wrote:
>
> >> On Tue, Jul 14, 2009 at 10:35:26AM -0500, Ryan Schmidt wrote:
> >>
> >>> You can use svnsync to transfer all or part of the repository to
> >>> another server. So you can either sync the whole thing to another
> >>> server with more disk space and then do your dump, filter
> and load;
> >>> or you can sync just the project you want to extract to the new
> >>> server and there's your new repository all ready to go
> (well, you'd
> >>> have to copy over conf files and hook scripts if you have
> them). At
> >>> least, I was led to believe you can now, with the latest
> Subversion,
> >>> sync just a part of a repository; I'm not sure what the
> syntax for
> >>> that is.
> >>
> >> $ svnsync help init
> >> initialize (init): usage: svnsync initialize DEST_URL SOURCE_URL
> >>
> >> [...]
> >>
> >> If the source URL is not the root of a repository, only
> the specified
> >> part of the repository will be synchronized.
> >
> > What would happen to the revision numbers? Will I have
> empty revisions
> > in the destination repository? Or will the revision be
> sequential and
> > therefore not in sync with the source repository?
>
>
> svndumpfilter has the options --drop-empty-revs and
> --renumber-revs to help you choose which of those behaviors you want.
>
> Um, I believe if you use neither option, the default is to
> keep your revision numbers as they were, and thus to insert
> empty revisions for the ones that are not relevant to your
> new thinned repository. If you want the revisions renumbered
> / compacted, then you use both -- renumber-revs and
> --drop-empty-revs. I'm not entirely sure what happens if you
> just use the one switch or the other, so I'm not sure why
> there are two switches.

Thanks Ryan, but I actually meant what happens to the revision number in case you use svnsync to synchronise just a part of the repostiory, not when dumping, filtering and loading a repository.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2371710

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-16 12:20:37 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.