No the repository has no branches. I did find the server where the
repository is kept had a clock that was 1 hour ahead of current time. (Not
sure how it got that way, it had shifted to Daylight savings time but was an
hour ahead). Anyway this is now fixed but the problem persists.
On Apr 22, 2010, at 7:29 AM, verizon wrote:
No the repository has no branches. I did find the server where the
repository is kept had a clock that was 1 hour ahead of current
time. (Not sure how it got that way, it had shifted to Daylight
savings time but was an hour ahead).
On Apr 22, 2010, at 7:29 AM, verizon wrote:
No the repository has no branches. I did find the server where the
repository is kept had a clock that was 1 hour ahead of current
time. (Not sure how it got that way, it had shifted to Daylight
savings time but was an hour ahead).
Hello Fossillies,
I have tried repeatedely to clone a large-ish repo (~170MB) over a 3G link
(fast digi cellphone link) - the link is pretty fast.
I can clone the repo on the server directly ok - so presume repo is ok.
My version is ...fossil version [73c24ae363] 2010-03-18 14:20:33 UTC
Any
More info - I get 43Megs (but this figure varies) then it just hangs - I
clocked link at 1440mbps
- Original Message -
From: Andy Reynolds a...@andix.co.uk
To: fossil-users@lists.fossil-scm.org
Sent: Thursday, April 22, 2010 7:03 PM
Subject: Fossil Failing to Clone 170 Meg Repo over 3G
What kind of error do you get? If you need a workaround, you can
transfer the repo file with scp or rsync (which can pick up where it
left off when interrupted) and then fossil sync them.
--
Joshua Paine
LetterBlock: Web applications built with joy
http://letterblock.com/
301-576-1920
6 matches
Mail list logo
