I've been lurking on this thread, collecting the valuable feedback. Thanks all. On Sun, Aug 3, 2008 at 12:06 PM, Brandon S. Allbery KF8NH < allbery@ece.cmu.edu> wrote:
On 2008 Aug 3, at 5:35, Andrew Coppin wrote:
Well Darcs already does that. So... what's to develop? It's not like it's
slow or buggy. I
Oh, two more under "buggy":
(a) as mentioned by others, the ghc repos often cause darcs2 to spin without doing anything. (This may secretly be the network library; strace looks an awful lot like my lambdabot when it gets stuck, but it's hard to tell because that may just be the thread scheduler.)
I just want to clarify one point about darcs1 vs. darcs2. The darcs2 program works on both darcs1 and darcs2 format repositories. When it works with darcs1 format repositories it works the way darcs has always worked on darcs1 repositiories. Thus, it's not fair to say that the above problem exists in darcs2 format repositories since the GHC repository was never publicly converted to darcs2 format. So, the spinning of the darcs2 program on the GHC repository is due to flaws in darcs1 format that have hopefully all been corrected in darcs2 format. Yes, this is a known bug, but also one that has received considerable effort, and is currently presumed to be fixed for darcs2 format repositories. Bug reports and test cases to the contrary are welcome. Jason