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

Re: Timeouts and such

From: <kfogel_at_collab.net>
Date: 2003-05-08 06:37:30 CEST

"Derek J. Balling" <dredd@megacity.org> writes:
> This combination seems "bad". In other words, it seems bad to me that
> it should be possible to get to this state in the first place,
> especially given that the syntax for the command is to apply the
> propset to a path, not a specific file.

No, this is a normal and sane Subversion state. Mixed-revision
working copies are common, and an expected result of committing
without updating.

What is the difference between "a path" and "a specific file"? :-)

> > For now, your only recourse is (probably) to do a fresh checkout, or
> > increase your neon timeout in your servers file.
> Yup, that was what I'd ended up doing. Although I ended up having to
> rollback my CVS->SVN migration after two days anyway. (full story
> here: http://www.megacity.org/blog/archives/000615.php for those who
> care)

Wow, sorry to read that:

   The problem, it turns out, appears to be that the crappy AIX box we
   do development on has shittier throughput than I might have using
   that Carrier Pigeon IP implementation. I'd always known that
   backups on the H50 take about 12 times longer than backups on the
   linux boxes do (and the linux boxen have about twice the data on
   them that the devel box does), but it'd never been a real "problem"
   until now.

(Hmmm, does Subversion do that much more I/O than CVS?)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 8 07:19:26 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.