Isnt there any retry ability on SVN? Cause the network might be slow or
unreliable, but most of the time, it worked. I could connect my remote
server with SSH and work for long time.
Since the nature of SVN is transaction based, it will be great if it could
cache the uploaded stuff somewhere on server, push the data up ( with
retries ), then submit in transaction over there. Otherwise, it is too easy
to break a big transaction in case like mine.
On 3/2/07, Mark Phippard <email@example.com> wrote:
> On 3/2/07, Li Ma <firstname.lastname@example.org> wrote:
> > Hi there,
> > I set out this question yesterday after I joint the mail list. But got
> > no response. Maybe it was lost. So I send it again. Please help me if you
> > have any solution on this.
> > I am in US and I have a repository in China. very often, I need to
> > submit large bunch of files ( 100M+ ) to the repository,especially when a
> > new project is started.
> > The network connection is about 30K byte per sec and very unstable. So
> > most likely my big commit will fail because of network connection. This is
> > very frustrating, because if network failed in the last M, the whole 100M of
> > transmission will be wasted.
> > I know SVN can handle slow network, but is there anyway to handle slow
> > and unstable network?
> My guess is that there isn't a solution which is why you did not get a
> Mark Phippard
Received on Fri Mar 2 20:33:12 2007