So, this is rather embarassing. I tried forking patch tag, as follows:
darcs get the patch tag code repo on local machine create new (empty) repo via the patch-tag interface darcs push to patch tag. The process hunt (10 minutes, no feedback). local machine: thart...@ubuntu:~/patch-tag-dev>darcs changes | wc -l 2210 thart...@ubuntu:~/patch-tag-dev>darcs --version 2.2.1 (release) thart...@ubuntu:~/patch-tag-dev> server: thart...@patch-tag:~/patch-tag>darcs changes | wc -l 2204 thart...@patch-tag:~/patch-tag>darcs --version 2.2.1 (release) thart...@patch-tag:~/patch-tag> I can successfully perform this action if pushing to a virgin local repo, takes about a minute. I can also push to patch-tag server if I wipe history and push just the files as a first commit. Still, this struck me as pretty bad behavior. Has anyone had similar experience, or is there documentations on the conditions that can lead to a hung push? How does darcs hold up when hosted in darcs? Any similar problems? If any of the darcs devs would like to have access to the patch tag repo to reproduce this themselves the are welcome. Doh! thomas. -- Thomas Hartman Darcs hosting: patch-tag.com Build a webapp with haskell: happstack.com _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
