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.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2371644
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-16 02:10:15 CEST