Hi...
Thanks for your reply.
cmpilato@localhost.localdomain wrote on 22.10.2003 15:15:23:
> Roland Schwingel <Roland.Schwingel@onevision.de> writes:
>
> > I have the feeling that when checking in both files at once svn
> > checks the whole working copy tree for changes, because the
> > harddrive where my working copy is acts like mad. Wheras with single
> > checkins this is not the case.
> >
> > Any ideas?
>
> I'm guessing this is issue #1245. While you are incorrect in assuming
> that your whole tree is checked for changes, we *do* have a known bug
> that would cause practically your whole tree to be *locked* (and later
> unlocked) during the commit process. This can take a long time.
Well you are the guru... :-)
What I have observed is, that my harddrive works like mad when doing my
mentioned action. And the bigger my repos is the longer it takes.
(I tried the same with smaller versions). So I was thinking it
might run here thru the whole tree, whereas it is not doing that when
doing single checkins.
Just wanted to post my observation (by hoping it might get on a list
of items to fix sometime). At present I am checking in splited what
means I have for the same change 2 (or more) commits, would be more
nicer to have them in which makes more sense if you look back
later in some years.
Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 22 16:58:31 2003