Re: New (1.5) feature questions -- things we need to address before a release can happen
From: David Summers <david_at_summersoft.fay.ar.us>
Date: 2007-10-23 05:14:37 CEST
A thread got started this last May about "things we need to address before
One of those is something that I run into sporadically (happened again
There was discussion about it at
When a large commit happens to the slave server (re-directed to the master
This happens 100% of the time if the commit is beyond some magic number of
Should I enter this as a problem in the issue tracker so we don't forget
Karl had some suggestions about a couple of different ways to fix it.
Is this something that would be "easy" to do?
It would be SUPER SWEET if this could be fixed for 1.5.0.
If it is "easy" (how easy?) then is it "byte-size" or something that
At the time I mentioned it this last May I was extremely busy but at the
The other problem I've had with master/slave web-dav proxy mirroring is
Should I enter this as an issue as well? This is only a problem when the
Thanks!
-- David Wayne Summers "Linux: Because reboots are for hardware upgrades!" david_at_summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt PGP Key fingerprint = 0B44 B118 85CC F4EC 7021 1ED4 1516 5B78 E320 2001 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org For additional commands, e-mail: dev-help@subversion.tigris.orgReceived on Tue Oct 23 05:14:52 2007 |
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.