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

Increasing verbosity and feedback on svn commit

From: Filipe Brandenburger <lists.filbranden_at_idilia.com>
Date: Wed, 28 Jan 2009 07:35:19 -0800 (PST)


I just migrated a huge repository from CVS to Subversion using cvs2svn. On the server the repository had ~210GB on CVS and shrunk to ~30GB on Subversion. Checkout size was around ~10GB in CVS and grew to ~20GB in Subversion, but this was expected as we knew it would keep two copies of the files.

So, nothing wrong with the migration, people are working in Subversion and I have positive feedback from when they tag a release, which before took hours to do and had to be done overnights otherwise it would kill production, and now takes a few seconds only.

The only thing I hear complains about is that Subversion is not very verbose in some cases. For instance, sometimes commits are very long (5 minutes), but Subversion does not tell what it is doing and I did not find any command line switch, config file option or environment variable that could do that. It only shows "dots", but even then, after it finishes printing the dots it sometimes spends a long time doing something, but there is no feedback on whether it is going forward or hung.

Is there any way to configure Subversion to give more feedback on these operations? Like printing the name of files/directories it is traversing? And after it stops printing the dots, what exactly is it doing? Is there any way to be able to see the progress in order to see that it is not stuck?

Thanks in advance!


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-28 16:38:48 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.