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

Re: moving project to a new repository

From: Nathan Nobbe <quickshiftin_at_gmail.com>
Date: Wed, 4 Mar 2009 15:26:59 -0700

On Wed, Mar 4, 2009 at 4:18 AM, Ilan Yaniv <Ilan.Yaniv_at_timetoknow.org>wrote:

> Aha, but svn dump and load moving the whole repository. I want a single
> project from the repository, and to have much less revisions.
> The thing is that currently in our SVN repository there are many projects
> and 28000+ revisions.
> So when a user wants to see a log, it takes him about 10secs to open the
> log, and about 20Min to create a Tree view.
> So, I thought that if I copy the projects to separated repositories, I will
> spend less time with going over revisions from other projects

have you tried using git as a front-end to svn? for repo browsing its
unbeatable. ive noticed trivial operations going way way faster, and tree
views dont take much time to render (on our repo min or two, tops) w/ gitk
--all, which show the contents of all branches, all revs period. we have a
repo w/ over 35k revs; on said repo, i can diff 2 branches in under a 10th
of a second..

i just got so sick of finding out a change came from a merge, having to then
go back to the previous branch, and find out that came from a merge etc.;
now i just click a button a few times and let git do all the work..

note the one lame aspect is it would take time to initially clone the repo,
maybe 5 hours or so.

im not trying to start a war here, but from my perspective, if i used git
simply for searching the repository, and nothing else, id be saving lots of
time. it also seems relevant, since this complaint was about performance,
and theres nothing wrong in using git in conjunction w/ svn, especially for
the parts where it really shines.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-05 07:10:35 CET

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.